Comment on page
Permissions define granular access rights to apps, services, data, environments and functionality within Appfarm Create.
- If a user can run a service from within an app, they need a role with access to the service.
Additionally, when you add a new role, they have no object class permissions at all, so you must grant the required permissions.
Be restrictive, and don't grant permissions that a role doesn't need.
Good to know
The built-in roles do not have access to Test, Staging, or Production.
If you've created a custom role that needs access to Appfarm Create, that can also be granted under Login access.
Manage permissions for adding, updating, and deleting users, service accounts, and individual roles. This includes assigning and removing roles.
If you have functionality in your apps or services for adding, modifying, or deleting users, the appropriate permissions must be granted here.
Good to know
When performing user management operations from inside an app or service, the built-in role privileges are not valid.
Advanced permissions include privileges within Appfarm Create. Typically, you would only use these if you create a custom role which requires access to Appfarm Create.
These permissions allow you to tightly control which parts of Appfarm Create that role has access to. For example, to allow access to only one specific app or restrict deploying to Production.
This is also where you can grant a role the permission Update Secret from Service. This is required when you have a service run by a schedule that fetches an authentication token from an external API and stores that token in a secret.