When we think of permissions within ServiceReef, it is important to differentiate between the different levels on the platform. Let's begin at the top!
1. Organization Admin: This is a user that has been added to your team by an approved administrator. They are then given ability to manage the following areas of an organization-see below.
An Organization Admin is someone who may create trips, manage the organizational level elements such as templates, forms, tasks, etc., manage finances and donations, groups, tracks, pipelines, and stories.
2. Team Admin: This is a user who is leading or managing a specific Opportunity. ServiceReef provides a lot of detailed controls for Team Admins on your trip. Once you have the right person selected, you can indicate if they should be notified on certain events and limit their permissions on various tasks. For example, you can allow them to see the donations for users (which helps as they can be your front line for any questions from the participants), approve or decline participants, etc.
This person can be an Organization Admin also but does not have to be one. An Organization Admin will need to assign a user to the role of a Team Admin within a specific Opportunity.
In order to add a Team Admin, you will click "Add Admin".
You will enter their name at the top and select what permissions that Team Admin will have.
3. Track Admin: This is a leader that is leading or managing a specific Track. A Track Admin must already have a ServiceReef account to be added as an admin to a Track. Admins will be alerted of new subscribers, track completions, and more. You can choose to list them as the Track Leader on the Track page, if they can manage/edit the Track, and if they can moderate Track discussions and approve new participants.
4. Pipeline Admin:
This is a leader that is leading or managing a specific Pipeline. A Pipeline Admin can be given permission to view and manage the information and stages as well as the ability to move members between stages. You can also give them permission to view only (essentially giving them behind the scene "eyes" but no management capabilities). Organizations can choose if a Pipeline Admin will be able to see all members or only those assigned to them.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article