Access control for user accounts
Introduction
AccelByte Gaming Services (AGS) uses roles, which enable you to manage user permissions and define which users can access the Admin Portal. A role is an association between a list of permissions and a list of users. As permissions cannot be directly defined on a user account, roles provide the mechanism for assigning permissions to a user.
Default roles
AGS includes several default roles that already have permissions and are ready to use. Each role contains its own permissions:
Default roles in Shared Cloud
In Shared Cloud, there are three predefined roles: Studio Admin, Game Admin, and View only.
Role | Admin | Description |
---|---|---|
User | No | A user that normally signs into the backend through the game, i.e., a player. When you create accounts, the system automatically applies the user role to give players the permissions they need to access resources within your game. |
View Only | Yes | Access to specific game namespaces. |
Game Admin | Yes | |
Studio Admin | Yes |
Default roles in Private Cloud
When you create a new publisher environment, it contains the following roles by default:
You can also create a new role with a set of permissions to match users' needs. That way, you can avoid users having access they don't need.
Role | Admin | Description | Permissions |
---|---|---|---|
User | No | A user that normally signs into the backend through the game, i.e., a player. When you create accounts, the system automatically applies the user role to give players the permissions they need to access resources within your game. | Full list of permissions here |
View Only | Yes | Read-only admin access to the Admin Portal. Has access to all namespaces. | Full list of permissions here. |
Game Admin | Yes | Full control, admin access to the Admin Portal. Has access to specific game namespaces only. | Full list of permissions here. |
Super Admin | Yes | Full control, admin access to the Admin Portal. Has access to all namespaces. | Full list of permissions here. |