To grant an organization limited access to a peer organization.

User accounts can be configured for restricted access to peer organizations by assigning a custom permission profile. This avoids the need to nest organizations in a parent/ child dynamic, which would grant full administrative access to user accounts in the parent organization.

The following example refers to sub-organizations of "Trade Demo," as depicted above. User accounts belonging to the "Operations" organization require limited access to devices in "Staging" and "Production" -- they need to be able to move routers between orgs as routers leave the configuration lab (staging) and go out for deployment (production), but access to other aView features should be disabled.

After adding roles with the relevant abilities to each target organization (e.g. Staging and Production), selective access can be granted to users in the "Operations" org based off of the shared permissions.

Organizations are populated with an administrative role by default. Admins should have access to all aView abilities, which isn't always the appropriate level of access for a given set of tasks.

Additional roles can be created to provide selective account permissions for users. To do so:

1. Navigate to the Organizations screen using the main menu.
2. Select Roles from the Actions menu of the organization intending to grant selective access. This will be either "Staging" or "Production" per the example outlined in the overview.

3. Click the Create button to add a new role -- be sure to only include abilities that are relevant toward the limited access.

After creating custom access to an organization by defining a limited role, the permissions can be granted to other organizations.

1. Navigate to the Organizations screen using the main menu.
2. Select Permissions from the Actions menu of the organization intending to receive selective access. This will be "Operations" per the example outlined in the overview.
3. Click the Create button to add new permissions to the organization.

4. Using the Organization pull-down menu, select the organization that is granting limited access.
5. Select the new role -- created in the first section of this document -- via the Description pull-down.
6. Verify the relevant Abilities are listed and click Create Permission to finalize the configuration change.

Once an organization has been granted permission to a peer organization, its users can be granted access to the peer organization.

1. Navigate to the Users screen using the main menu.
2. Select the intended user account by clicking on its email address or the Edit button.
3. Browse to the Permissions tab of the user account.
4. Click Create to add access to the peer organization, selecting the relevant Organization and Role per the intended scope of access.
5. Select Create Permission to finalize the configuration change. The user is now able to interface with the peer organization per the Abilities that correspond to the organization's entry in the permissions table.