Access control
The permissions of a team are configured in Settings › Teams. They apply to the users of the team; admins and developers always have full access.
Permissions are signed by Adminmate and checked by your Data API on every request, so a user cannot bypass them from their browser.
Environments
Section titled “Environments”Choose the environments the team can open, for example only production for your support team. A team needs at least one environment.
Sections
Section titled “Sections”Choose the parts of Adminmate the team can use:
| Section | Content |
|---|---|
| Data | The data explorer, item pages and actions. |
| Dashboard | Dashboards and charts. |
| Collaboration | Comments and mentions. |
Models
Section titled “Models”Choose the models the team can see. A model that is not selected is hidden from the team, and the Data API refuses to list or open its records for its users.
For each selected model, choose what the team can do:
| Permission | Allows |
|---|---|
| Create | Creating new records. |
| Update | Editing records: all the fields, or only some of them. |
| Delete | Deleting records. |
| Configure | Changing the display of the model: columns, field settings, item overview. |
| Segments | Using all the segments of the model, or only some of them. |
| Actions | Using all the actions of the model, or only some of them. |
Model options set in the Data API come on top: if canDelete is false for a model, nobody can delete its records, whatever the team permissions.
Example
Section titled “Example”A support team that must help customers without being able to break anything:
- Environments: production
- Sections: Data, Collaboration
- Models:
userswith Update limited toemailandphone, and the actionsresend_confirmation_emailandreset_password;ordersread-only with the actionrefund.