Adeptia Connect provides user to have a role-based access. You can create a role to define the access to the activity and user rights may vary depending upon their role defined.

While creating a role you have flexibility to create a role specifically for a company or partner. There is a possibility that one user is managing more than one company/partner, and this user needs different roles and permission. For example, a user may have access to create a transaction for a specific partner, but for another partner same user can only view the transaction.

To understand it better, say there are two users namely Andy and Michelle and both are are managing two Partners (e.g. Walmart, Target) transaction. Andy is managing Walmart’s transaction sand Michelle for Target’s . In this use case the requirement is such that Andy can't see the Transaction which Michelle is creating or managing and vice versa. We can manage this by creating users in GAC with following rights:

User	Company/Partner	Role	Permission
Andy	Walmart	Account Administrator	L/R/W/E (Transaction)
Andy	Target	File Submitter	R/E (Transaction)
Michelle	Target	Account Administrator	L/R/W/E (Transaction)
Michelle	Kohls	File Submitter	R/E (Transaction)

Users can be assigned to multiple roles as per the requirement and while login, select the specific role to login.

Only a System Admin and an IT User can create role.

Steps to create a Role:

Go to Account and click Roles.
Click Add Role.
On Create Role screen, enter the name and description of the new role in the text boxes of Role Name and Description respectively.
You can create a role specifically for a company or partner by selecting Role Type as 'For Company' or 'For Partner'.
Select the Base Role from the drop-down list of Base Role to define the permission.

If you are creating a role for Partner then select the base role as 'Partner IT User' or 'Partner Business User' from the drop-down list.
Select the project from the drop-down list of Project Access. By default, the Project Access drop-down list box displays the default project of the logged-in user. If you do not provide access to any of the listed projects then the access will be added in the Default project of the logged-in user. Click here to find more on Project Support.

You can select the multiple Project from the drop-down list for which you want to have access.
Select the Network for the role you are creating from the drop-down list of Network. To select multiple Networks from the drop-down list, click on the networks one by one. User(s) associated this role will be able to manage only selected network(s) while working on the Networks page in Connect.
Select the Networks for the role from the drop-down list of Network List. Selected network(s) will be shown in the list wherever the user needs to choose the network(s). Networks selected in the above step will automatically be added to Networks' list.
Select the 'Define permissions for custom entities' checkbox for defining custom entities permission.

'Define permissions for custom entities' checkbox is visible on Create Role Interface only when custom entities are already created by the user.
Click Next to define the permissions.
On Define Permissions screen, click to view the detailed guidelines on defining the permissions.
1. Select the checkbox Allow Login into Developer Studio if you want user to have access of AIS through Connect portal.
2. By default, permissions checkbox are selected based on the selected Base Role. Click here to view the detailed guidelines on defining the permissions to the users.
3. You can update the permissions to create a role for the user to access those activities.
Click Next to define the permission for Custom Entities. By default, no permissions checkbox are selected.
You can define the custom entities permission by selecting the listed permissions column as:
1. All
2. View Tab/Link
3. List & Read
4. Create
5. Edit
6. Execute
Click Save. A message is displayed confirming that the Role has been saved successfully.
Once Role is created, you can view the summary of Role Definition and Permission. To know about viewing role details, click here.

Browser not supported