Configuring Permissions

Permissions for users and roles can be configured from the user interface on the Users grid and Roles grid.

In edit mode, you can add and delete users and roles.

For information on enabling, assigning, and revoking permissions as well as monitoring permissions, see Permissions.

For the consequences of modifying the permission configurations, see Required Permissions for API Calls.

Users Grid

Column	Description
User	The FTL client's user name.
Resource	The identifier of the defined resource. Example: Resource = ftl.nonpersistent.store
Resource Type	The type of resource including persistence stores and eFTL channels. Example: Resource Type = Persistence Store
Resource Belongs To	The name of the object. The resource belongs to a persistence cluster or eFTL cluster, so in that sense it belongs to a service that is that servicing this cluster. Example: Resource Belongs To = ftl.default.cluster
Permissions	The permissions granted. Requirements: The FTL server must have TLS and authentication enabled. See Permissions. The Realm Properties Details Panel, Permissions must be set as Enabled. See Realm Properties Details Panel. At the persistence cluster level, the value is `lock`. At the persistence store level, the value can be: `publish` `subscribe` `map`

Column	Description
Roles	The FTL client's role.
Resource	The identifier of the defined resource. Example: Resource = ftl.nonpersistent.store
Resource Type	The type of resource including persistence stores and eFTL channels. Example: Resource Type = Persistence Store
Resource Belongs To	The name of the object. Example: Resource Belongs To = ftl.default.cluster
Permissions	The permissions granted. At the persistence cluster level, the value is `lock`. At the persistence store level, the value can be: `publish` `subscribe` `map`

Did you find this helpful?

Yes No