Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Admin Rights

If you have Admin status on Voluntarily you will see these changes in the system

Client Interface

  • Footer - shows menu to admin page and other entity pages.

  • MemberSection - Admins and orgAdmins see the member table of an organisation

  • adminPage - access to any page wrapped in the adminPageHOC

  • ActDetailPage - owner, OrgAdmin and Admin can edit the Activity

  • OpDetailPage - owner, OrgAdmin and Admin can manage the Opportunity: edit, manage interested volunteers, complete and cancel

  • OrgDetailPage - OrgAdmin and Admin can edit the organisation

  • OrgDetailForm - Only Admin can edit the organisation category. category cannot be set to Admin except through db config. Orgs cannot make themselves Admin OP or AP and they are VP by default. A system Admin must edit the organisation to make them a school or Activity provider based on a formal request. or they are onboarded into that mode directly.

  • OrgListPage - Create Organisation button.

  • PersonDetailPage - Admin has newPerson Edit, Remove & ShowPeople buttons.

Admin Pages

  • admin/invite-school

  • admin/goals

API

Admins can

  • list/get all entities

  • create/update all entities

  • delete all entities

  • carry out OrgAdmin functions for all organisations

  • carry out owner functions for activities and opportunities

  • view and modify person record

Admins cannot

  • no current restrictions

How to get Admin Status

To be admin you must have role = [Role.ADMIN] set in your Person record.

Explicit Admin role

Create person sets role to Volunteer.

role cannot be set through API PUT calls as the field is deleted before save.

role can be set by direct editing of the person record in the database. This allows devs to set their admin status directly. It also allows the first administrator to be created in a new deployment by someone with database access.

Implicit Admin 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 admin role you must be a MEMBER of and not ORG_ADMIN of the admin 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. VP-1110 - Getting issue details... STATUS

  • No labels