...
| Code Block |
|---|
http://alpha.voluntarily.nz/api/people?q={ "role": "support" }&s="name"&p="name email" |
...
Org Admin Rights
If you have Support orgAdmin status on Voluntarily you have these abilities :- but only for the organisation that you are admin for.
Client Interface
Footer - See menu to admin page and other entity pages.OrgDetailPage - can edit the organisation
MemberSection - See the member table of an organisation
supportPage - access to any page wrapped in the supportPageHOC - TODO
ActDetailPage - can edit the Activity if your org is an Activity Provider and the activity was created by a member of your organisation.
OpDetailPage - if your org is an opportunity provider you can manage the Opportunity: edit, manage interested volunteers, complete and cancel OrgDetailPage - can edit the organisation - for ops created by your members.
OrgDetailForm - Cannot edit change the organisation category. category cannot be set to Admin except through db config.
OrgListPage - Cannot see Create Organisation button, cannot delete an org
PersonDetailPage - Can List people and edit people. Cannot delete.
Admin Pages
admin/invite-school - NO
admin/goals - No
Support Pages
TBD
API
...
Org Membership Admin Pages
The orgAdmin can see the members tab on the organisation page, can use this to add or remove followers, move people from join/validation requests to members, can make members orgAdmins.
Can download a list of all members as CSV file for export.
API
OrgAdmin can
list/get all entities/update all entities
carry out OrgAdmin functions for all organisations
carry out owner functions for activities and opportunities
view and modify person record
...
created by people belonging to the organisation and where the org is the offerOrg.
can list/get/update their own organisation record.
OrgAdmin cannot:
delete all entities
create new people, organisations.
set organisation category
Enabling
...
OrgAdmin Role
To be a support an OrgAdmin person you must have role = [Role.SUPPORTORG_ADMIN] set in your Person record or be a member of an org with the Admin (AGENCY) Category.
Explicit Support role
When a person first signs in they are given the default ‘volunteer’ role.
The support role cannot be set through API PUT calls as the field is deleted before save.
Support role can be set by direct editing of the person record in the database. This allows devs to set their support status directly.
x/db/make-admin.js (Give a person the "admin" role) - TODO update to create support staff
However subsequent support staff should have their role set by membership of a support organisation. This makes it easier to add and remove new support staff.
Implicit Support role
People inherit their role and access permissions from the organisations they belong to. Hence an org with ‘admin’ category has members who will have the admin role. This allows us to create an org for ‘voluntarily support’ and to manage people in this role without needing database access.
Note to get support role you must be a MEMBER of and not ORG_ADMIN of the support org.
Setting the category of an organisation can only be done by an existing admin. Hence only an existing admin can create a new admin organisation. Jira Legacy
To be an orgAdmin you must first be a member of the organisation and then have your role set to OrgAdmin by a system administrator, another existing orgAdmin or through an invitation email.
You cannot remove your own orgAdmin status.
The school-invite email creates both a new school organisation and makes the person responding to the invite the first orgAdmin for that school.
The member-invite email can be sent from an organisation members page to invite others to also be orgAdmins.
Recovery of an organisation account
Should for any reason an organisation lose access to their orgAdmin account e.g. by a person leaving etc. A support request should be issued asking for another existing member to be promoted to admin. This request should contain sufficient documentation to justify the change.