Control Center - System – Managing Access Profiles and User Access (new)

Purpose

Access Profiles define the permissions that users have in Uneevo.

Administrators create and configure an Access Profile first, defining the modules, actions, company scope and data restrictions that it provides. The profile is then assigned to individual users, ensuring that access is consistent with each user’s role and responsibilities.

This article explains how to create Access Profiles, configure their Access Rules and assign them to users.

Important

Access Profiles control access to Uneevo data and functionality. Configure them carefully and assign only the permissions required for each role.

💡Important: Changes to an Access Profile affect all users associated with that profile.

Access Path

To manage Access Profiles, go to:

System → Access Profiles

Overview

The access-management flow follows three steps:

Create an Access Profile for a specific role or access requirement.
Configure the Access Rules that determine which actions and data the profile can access.
Assign the Access Profile to the relevant users.

For example, you may create separate profiles for Project Managers, Sales Users or System Administrators, each with the appropriate level of access.

Access Profiles Landing Page

The Access Profiles landing page displays all configured profiles.

The following information is available for each profile:

Column	Description
Name	The name used to identify the Access Profile.
Description	A short explanation of the role or purpose of the profile.
Users	The users currently associated with the profile.

Use the available filters, refresh, export and column-selection options to find and manage profiles. Select Include Deleted when you need to view deleted profiles.

Creating an Access Profile

Select Add Access Profile.

Complete the following information:

Field	Description
Import Access Profile	Optionally select an existing profile to use as a starting point for the new configuration.
Name*	Enter a clear and unique name for the Access Profile.
Description*	Describe the role, access level or intended use of the profile.

Select Save to create the profile, or Save and New to create another profile immediately afterwards.

💡 Tip: Use role-based names, such as Project Manager or Sales User, so administrators can easily understand the intended access level.

Configuring Access Rules

After creating the profile, open it to configure its permissions.

The profile details include:

Field / Element	Description
Name	Identifies the Access Profile.
Description	Explains the profile’s purpose and intended use.
Users	Displays the users currently associated with the profile.
Has All Permissions	Grants access to all available actions within the selected companies and restrictions.
Scopes	Defines the organisational scope to which the permissions apply.
Conditions	Defines conditions that may further limit access.

Granting Full Access

Enable Has All Permissions when the profile should have access to all available actions.

This option still applies the selected company scope and restrictions. Bundle permissions are retained and may provide additional access.

Use this option only for roles that genuinely require broad access, such as system-administration roles.

Configuring Module Permissions

When Has All Permissions is disabled, permissions can be configured individually by module and functional area.

For each module or area, you can define:

Permission	Description
Read	Allows users to view information.
Create	Allows users to create new records.
Update	Allows users to edit existing records.
Delete	Allows users to delete records.
Companies	Defines the companies to which the permission applies.
Restrictions	Defines any data-access restriction applied to the permission.

Use the search field to find a specific module or area. Modules can be expanded to configure permissions at a more detailed level.

The available filters help administrators review the configuration:

All modules
Selected
Not selected
Collapse All
Expand All

Assigning an Access Profile to a User

Once the Access Profile is configured, assign it to each relevant user.

Open the user record and select the appropriate value in the Access Profile field.

Field	Description
Access Profile	Defines the permissions and access rules applied to the user.

Save the user record to apply the selected Access Profile.

The profile’s Users field provides visibility of the users currently associated with that profile.

💡Important: Assign a user to the profile that best reflects their role. Do not use a full-access profile simply to resolve an individual access request.

Best Practices

Create profiles based on business roles, rather than individual users.
Apply the principle of least privilege: grant only the access required for the role.
Use clear names and descriptions to distinguish profiles.
Use company scope and restrictions to limit access to the appropriate data.
Review the users assigned to each profile regularly.
Review profiles with Has All Permissions regularly and restrict them to authorised administrative roles.

The following setup illustrates how these principles can be applied to a typical Project Manager profile. Access is centred on managing the user’s own projects and assigned project portfolio, without allowing changes to master data, users, or global system settings.

Module	Recommended access	Restriction	Rationale
Assessment Planning	Read	All companies / assigned company	Consult assessment plans and requirements.
Entities Management	No access	—	Legal entities and organisational setup should remain admin-managed.
People Management	Read; optionally Update	Only project-team members / own content	View team skills, availability and assignments; avoid creating or deleting people records.
Sales Management	Read	Assigned company / own content	Visibility over approved opportunities or estimates that may become projects.
Project Management	Read, Create, Update, Delete	Only own content	Core PM access: create projects, manage scope, dates, budget, team and status.
Resource Management	Read	Only own content / assigned projects	Request resource allocations for their projects.
Operations Management	Read	Only own content	Track operational/project delivery information without changing central operational data.
Insights	Read	Only own content / assigned projects	Monitor project KPIs, financials, utilisation and progress.
General	No access, unless needed	—	Enable only any required shared features.
System	No access	—	System configuration must remain restricted to administrators.
Activity Planner	Read, Create, Update, Delete	Only own content	Plan and manage their own project activities and follow-ups.

The most important control is applying Only Self Content where appropriate, particularly in Project Management, Insights and Activity Planner. This allows a Project Manager to manage and monitor the content within their responsibility while preventing changes to content owned by other managers.

Permissions in People Management and Resource Management should be confirmed according to the organisation’s operating model. For example, a Project Manager may only need read access to people and resources, while update access should be granted only where they are expected to maintain team details or resource allocations directly.

Managing Users
Managing Companies
System Configuration