> For the complete documentation index, see [llms.txt](https://learn.capstorm.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.capstorm.com/copystorm-director/reference/copystorm-director-gui/access-control.md).

# Access Control

The Access Control tab is used to configure access control/authorization for the core CapStorm applications (CopyStorm, CopyStorm/Medic, CopyStorm/Restore, and CopyStorm/Director). The Access Control editor table can be used to add new and edit existing CapStorm application users and assign pre-defined roles to users. These pre-defined roles will determine the level of access (available functionality) granted to the assigned user when using the aforementioned supported applications.

**NOTE: This functionality is disabled if using the desktop Swing GUI version of the application suite. In this case, the Access Control tab will be grayed out.**

## Step 1: Add a User

Click on the “Add User…” button.

![](https://4094748065-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F762n2rpeqXwJ3ygR1d80%2Fuploads%2Fgit-blob-ebdf702863999ca1f67284a1aed4042c33eb1541%2F13241ac2-main_access_control.png?alt=media)

This will open a pop-up dialog where you can enter the following:

* Username — a unique username.
* Password — a strong password.
* Enabled — this checkbox determines whether the user will be enabled or disabled upon creation.

Then click the “Save” button to add the user.

![](https://4094748065-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F762n2rpeqXwJ3ygR1d80%2Fuploads%2Fgit-blob-77813a8a94c000bd0cf14bc86f7e86ce9d122ca5%2F453004c9-add_user_popup.png?alt=media)

## Step 2: Assign the User a Role

After adding a user, you can assign the user a role.

![](https://4094748065-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F762n2rpeqXwJ3ygR1d80%2Fuploads%2Fgit-blob-aebd58003110cf5d42030e351bf84bcb7152b091%2F7b9cdc82-after_user_added.png?alt=media)

Three pre-defined roles are available:

* Super Admin — a top-level administrative role. A user with this role can perform any operation in any application **including** *configuration of Access Control.*
* Admin — a slightly restricted administrative role. A user with this role can perform any operation in any application **except** *configuration of Access Control.*
* Configurator — a user with this role can edit configurations for all applications, but cannot invoke any of the applications (cannot run jobs).

![](https://4094748065-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F762n2rpeqXwJ3ygR1d80%2Fuploads%2Fgit-blob-0b4aaea5a23cec0d73e62259bd40ca3f8393c3fd%2Fe184b499-role_selection.png?alt=media)

![](https://4094748065-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F762n2rpeqXwJ3ygR1d80%2Fuploads%2Fgit-blob-c3b084c5aa50fad88ce130aa61d37a911930da86%2F1a7bef43-access_control_role_popup.png?alt=media)

The “Production Enabled” check-box will enable/disable any operation that is allowed by the assigned role against a production database or Salesforce org. For example:

* A user that has been assigned the “Configurator” role but has the “Production Enabled” check-box *unchecked* **cannot** edit a production configuration.

A user can be enabled/disabled by clicking the “Is Enabled” check-box or deleted by clicking the “Remove” button.

![](https://4094748065-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F762n2rpeqXwJ3ygR1d80%2Fuploads%2Fgit-blob-d742ca17e376853fd400e5c1c4e22cce65d5df48%2Fdc101ef0-remove_user-1.png?alt=media)

## Step 3: Save Changes

When you are finished making changes to the Access Control configuration, click the “Save Changes” button at the bottom of the editor table. A pop-up dialog will appear where you can validate and confirm/deny all staged changes.

![](https://4094748065-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F762n2rpeqXwJ3ygR1d80%2Fuploads%2Fgit-blob-b8d064195840640a6ff9a24dd9d74471a3fe2e8b%2F6229e9c7-confirm_changes.png?alt=media)

You can also undo all staged changes by clicking the “Undo Changes” button.

![](https://4094748065-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F762n2rpeqXwJ3ygR1d80%2Fuploads%2Fgit-blob-b35fa82980beb89ec2d7b0e7a16cd85fcf47a76c%2Ffffe880c-undo_changes.png?alt=media)

## Access Control Database Schema

The Access Control configuration is stored and reflected in a sub-schema of the CopyStorm/Director database schema that consists of the following five tables and a single view:

* users
* authorities
* groups2
* group\_authorities
* group\_members
* user\_group\_authorities\_view (view)

These tables, and the view, are required for the functionality of the Access Control subsystem to function properly.