Skip to content

Remote User Teams

Users in globally distributed companies may find that they do not have sufficient network performance to work on some of the servers within the company. By redirecting users to different schemas, users can be redirected to servers that are closer to them geographically. User licensing can still be maintained from one server and one license file, as the license check does not require a particularly fast network connection.

If the users in different regions share cost data, and they need to regularly import and export scenarios to stay current with their colleagues, then different deployments can be kept consistent using the aPriori Scenario Synchronization functionality. See the Guide to Scenario Synchronization which is available from the aPriori Community Site (https://www.apriori.com/customer-knowledge-database/product-documentation/) or contact your aPriori representative for more information.

Granting Permissions to Deployments and Access Control

One of the reasons to use deployments is to control access to different schemas. Consider the following example of two schemas used by an aerospace company:

  • One schema is called “Civilian” and contains data pertaining to parts used in civilian planes.
  • The other schema is called “Military” and contains data pertaining to parts used in military planes.

It is possible that data in the “Military” schema can only be accessed by users with the appropriate security clearance, or users who are resident in a certain country. In this case, access to the “Civilian” schema could be granted to all users, but access to the “Military” schema would only be granted to the appropriate users.

Using deployments to segregate data performs a similar role to aPriori Access Control, as it allows administrators to specify what data can be accessed by each user. Using deployments is limited however, as access can only be controlled at the schema level, and any user granted access to a schema will have full access to that schema.

Access Control allows administrators to grant permissions on a much more detailed level. Users and groups can be granted a range of permissions such as “create”, “delete”, and “cost using”, and these permissions can be granted on a much more detailed level. See the Access Control chapter for more details.