Managing System Users

Creating Users

Creating users for your system is a simple process. First, select the “Auth” tab for your system. You should see something like the following:

click on “+User”. In the dialog that appears, enter a valid email address (eg myUser@myDomain.com), a password, and a password confirmation. Tap on “Register New User”. You should see a new row in the users table that looks something like this:

Each newly created user is assigned one role by default: ~Authenticated~. You can change the roles to which the user is assigned by clicking on “View/Edit” for that user. Doing so brings up a dialog that looks something like this:

This dialog shows that “myUser” is assigned the “Authenticated” role. To unassign that role, click on the “x”. To assign more roles, click on the “Add Roles:” popdown menu and choose from any of the existing roles and tap on “Add Role”. You may do this repeatedly. When you are finished. Tap on the “Close” button.

Note that you cannot create roles from this dialog. You can only assign and/or unassign existing roles. See “Creating Roles” below for instructions on creating roles.

Creating Developers

The process for creating developers is different from creating regular users. With the ClearBlade platform, a new developer first receives a registration key, and then signs up using that key. Here is how it is done using the console:

1. The developer goes to the main ClearBlade page for his or her installation. The page should look something like this:

Click on “Sign Up” on the upper-right portion of the page. You will be presented with the following form:

Enter valid information for every field in the form and click on the “Register” button. You’re now an official ClearBlade developer. The first thing you’ll want to do is …Link to creating a system…

Creating Roles

ClearBlade uses a rolls-based permissions model. Roles are created and permissions are assigned to them. Those permissions correspond to operations on various resources.

Note that users may have multiple roles. So, if a user has a role that has certain permissions and has another role that doesn’t, the user will have the permissions, even though one of their roles doesn’t specify them.

Roles can be managed from many different places in the console, but we will focus here on the roles management process under the “Auth” tab.

First, we need to go to the appropriate screen. First, select the “Auth” tab on the system you are working on. Next, click on the icon in the upper left of the screen and select “Roles” in the navigation bar. The following page will appear:

The contents of this page deserve explanation. Each row corresponds to a role in the system. Each system has three pre-defined roles: Authenticated, Anonymous, and Administrator. When you click on “Edit” within a cell in the table, the action is determined by the column in which the cell is contained as follows:

• Collections: You can select a specific collection and set create, read, update, and/or delete permissions for that role on that collection.
• Services: You can select a specific service and specify whether the role has execute permission.
• Users: Here you specify what permissions (CRUD) the role has on the entire users table.
• Message History: Here you specify the CRUD permissions the role has on the message history.
• Push: This specifies whether or not the role can use the push messaging system.