Arbor - Business Roles

Modified on Tue, 23 Jan 2024 at 09:52 PM

Business Roles in Arbor are what control the access permissions of the users. The roles are based on what most people who work in a particular position require. Such as a Cook may only require extremely basic access, but a teacher will require assessments and registers. 


This article will require you to be able to browse to staff profiles. 



When you create a user, you will be required to provide a business role, or the account will not be able to be created. If a user does not have a valid business role as they have expired, the user will not be able to sign in.

To assign a new business role:

    - Browse to the staff member's profile.

    - Filter or scroll down to current business roles.

    - Select New and fill in the side Window. 

    - Remember to fill in the end date or you can leave it as ongoing.






To edit the end date or end a business role:

   - Browse to the staff member's profile.

    - Filter or scroll down to current business roles.

    - Select the business role you would like to edit and click edit in the top right of the side window.

    - Change the end date and click the Save changes. To end the business role, set the end date to when the person ended that role.









Ad hoc permissions and roles.

If a staff member requires specific permissions which would not require them to have a specific business role, or they are not in a specific job role, but you would like them to have the permissions of that role. You can assign them on an Ad hoc basis. 

    - Browse to a staff profile.

    - Select Roles and Permissions from the left menu on the screen.

    - Select either Business Roles or Permissions.

    - Select the green in the top right 'Assign Permissions' or 'Assign Ad Hoc Permissions'.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article