Skip to main content
All CollectionsGetting StartedAccount Management
Team Member Roles and Permissions
Team Member Roles and Permissions
Updated over a week ago

Navigation tree: Settings > Account > Team Members

The team member roles and permissions allows any organisation on the AgriDigital Platform to easily manage the access levels for their team members.
โ€‹
The AgriDigital Platform has defined 3 standard roles which can be assigned to team members, Admin, Full User and Restricted User and these are explained in more detail below.

Roles Overview

Admin

The admin role of an organisation's account and can manage their settings, team members, integrations as well use all capabilities the organisation is subscribed to.


The Administrator is the only Team Member who can:

  • Create team members and assign them a predefined role (Admin, Full User, or Restricted User)

  • Update an existing team members role

  • Deactivate and reactivate team members

  • Create custom permission templates specific to their organisations requirements (Beta feature).

  • access the 'Bank Accounts' section in the Settings module.

  • edit the W/A Value in Inventory

More than one Team Member can hold the Role of Administrator.

Full User

The full user role of an organisation's account enables that user to use all capabilities the organisation has subscribed to.

Restricted User

The Restricted user role of an organisation's account has limited capabilities based on assigned permissions. We have setup some common restricted user templates which you can use to assign to your team members without needing to create your own templates, these include:

  • View Transactions & Storage

  • View Transactions only

  • View Storage only

  • Manage Transactions Only

  • Manage Storage Only

To view the specific permissions for these restricted user templates, click the view button located adjacent to the template dropdown (as shown in below screenshots)


โ€‹

Custom Permission Template

You can setup your own template which is explain in our custom template article.

Did this answer your question?