See users, groups, resources and policies in one place. Know who has access to what, why they have it, and how it was granted – without clicking between screens.
Groups and employees define who. Resource sets define what. Access policies define how.
No logins and no access rules – groups are only used to organise employees.
Organise the logins you want to share in Resource Sets.
Connect groups or individual employees to a Resource Set, apply an access policy, and get a complete overview of who has access to what.
Finance needs access to 30 logins, while Management only needs 10. Split the resources into two Resource Sets and give each group access to the sets they need.
Resource Sets are created once and shared with multiple groups under different access policies.
Organise logins into sets.
People or groups who need access.
Each connection has its own policy with permissions and restrictions.
Essential finance systems used by everyone in Finance and Management.
Additional tools used only by the Finance team.
Needs access to all 30 logins.
Needs access to 10 essential logins.
No restrictions. All actions allowed.
No restrictions. All actions allowed.
Limited access. Cannot share or edit.
Build Resource Sets around how you want to share resources. Share the same set with multiple groups under different access policies.
Access is granted when you connect a group to a resource set and apply a policy. Same resource set, different policy, full visibility.
Open any resource set to see exactly which groups and individuals are connected to it – or start from a login or a group and get the same view in reverse.
Every resource set shows exactly which groups and people have access.
Access is granted by connecting a group to a resource set and applying a policy – not by editing the resource itself. The same resource set can carry different policies for different groups, so the full chain is always traceable: User → Group → Policy → Resource Set → Login.
Connecting a group to a resource set – apply the same policies and permissions to every group, or set different ones for each.
Audit logs are tied to the view you're in. See changes, usage and admin actions directly, and prepare audit answers without manual digging.
Every action is logged with who did it, and when.
Joiners get access through the right groups. Movers have old access removed and new access granted. Leavers have everything removed automatically.
The same core question – who has access, why, and how – answered from three different starting points.
For any access, you can see the complete path from user to login – no hidden or unclear access.
Uniqkey's group model works well for straightforward access. You create a Finance group, add the right people, add the right logins, and set the permissions that apply. For many organisations, that's enough.
The limits show up when the same resources need to be used differently across the organisation. A Finance group might contain 30 Finance logins. The Finance team needs access to all 30. The CEO needs access too, but with different permissions. Management might only need 10 of the 30. An external accountant needs temporary, restricted access to five.
Today, each of these relationships is built as another group around the same resources. As access needs grow, so does the number of overlapping groups built around the same logins.
The model can still represent the access. The problem is that it becomes increasingly difficult to manage and understand.
There will be a "Migrate now" button in the platform. We'll also send reminder emails leading up to the migration.
Your groups stay groups. Your existing logins are organised into resource sets. Access that exists today stays the same – including your current policies and permissions, all of it is carried over. Your employees won't notice anything.
No, your employees won't notice a thing. Admins will – the interface changes slightly, and access is managed from a few different places in the Admin Portal.
We recommend that you migrate. Improved Access Management is where we're taking access management in Uniqkey going forward.
As organisations grow, the same resources often need to be shared differently across teams, which today means building overlapping groups just to represent different levels of access. We wanted to make it easier to manage and understand access, so we made the resource itself, not just the group, a first-class part of the model.
Feel free to reach out to your designated Customer Success Manager, or contact support@uniqkey.eu. We'll help you as fast as possible.
Email support@uniqkey.eu or get in touch with your Customer Success Manager.