Do we need a separate instance for each of our locations?
Some multinational organizations would prefer to manage one instance of Replicon, rather than one implementation for each location.
Whether or not using a single instance is possible depends on the organization’s requirements; Some of our multinational customers use one instance, while others require multiple instances.
Some Replicon features are easy to configure for multiple locations within a single instance, while other features must be shared. Refer to our Global vs Local Replicon Settings (XLSX | PDF) spreadsheet for information on which features fall into each category.
Note that in this document:
- Global settings are fixed Replicon settings that are used across the product, while
- Local settings can differ for each user, project, or group
Features that help if you want to use a single instance
- Nearly all Replicon features, including administration features, can be hidden on a per-user basis, since all access is tied to permissions.
- Many Replicon features are assigned either directly or indirectly to users (via templates or user profiles). This means you can easily assign each user location-specific settings.
- You can use group assignments to limit a user’s access to other users or projects by location. For each role they’re assigned, a user can be allowed access to all users or any subset of users, based on the group or groups users are assigned to.
For example, an administrator can be allowed access to only users in New York and Los Angeles, if those two location groups are defined in your system.
These limits are defined on a per-user basis, in user profiles.
The only roles that can’t be limited in this way are supervisors and billing managers, though supervisor access is already limited to direct reports.