Limiting access to projects using groups

  • 1
  • Article
  • Updated 2 years ago
Maybe you’re a multi-national, with offices across the globe, but only a small group of people truly needs access to your organization’s project data for all locations.

Or, maybe you’re a smaller company, but you don’t want Joe from Timbuktu who manages only local projects to be able to see all of your company's project data.

Limiting access to data has the following benefits:

  • It improves security by blocking managers from seeing data they don’t need
  • It unclutters the manager’s interface, so they can more easily find the data they do need
  • And finally, it reduces the risk of errors
Replicon already offers permission restrictions that limit what projects a user can access -- for example, a project manager can be limited to seeing only projects they manage. But sometimes those kinds of restrictions aren’t enough.

That’s why we’re very pleased to offer a new way to limit access to projects – using Replicon groups.

Groups are flexible, customizable categories you can use to reflect any kind of grouping important to your company, like locations, divisions, cost or service centers, or any other grouping you might need.

But most importantly, you can use groups to limit access to data; By assigning projects to groups, you’ll soon be able to limit which projects each manager in your system can view and edit.

For example, you’ll be able to let a manager work with projects linked to your Houston office, but not projects from your Calgary office.

We’ll let you know in the release notes when this feature is available. In the meantime, refer to Setting up user groups for information on our existing user groups functionality.
Photo of Paula Tannahill

Paula Tannahill, Technical Writer

  • 324 Posts
  • 2 Reply Likes

Posted 2 years ago

  • 1

Be the first to post a reply!