E. Access Levels

Access Levels define how Users and Roles are permitted to interact with Folders and Entries.

Have Questions?  Contact Us!

Each Access Level combines a set of allowed actions and grantable actions which get assigned as a whole unit.
Each access row has two parts: A ("Action") permits the action itself, while G ("Grant") permits the holder to assign the corresponding A action to other users.

Access is inherited: "Full" access on a folder means "Full" access to all of its contents (Entries, Subfolders, sub-Subfolders...) unless that inheritance is explicitly Blocked.

Assigning Access Levels

Access levels must be assigned to become effective. Access is assigned from a folder or credential, to a user or role.

Modifying Access Levels

Access Levels can be viewed or modified from the Web Admin client here:

Community editions do not allow the default Access Levels to be modified.

Default Access Levels

Included in all editions

 

Included in Enterprise or higher editions

 

Community Edition, includes three built-in access levels:

Enterprise Edition or higher, includes an additional access level:

Also allows the ability to create or modify Access Levels (via the "Access Levels" tab).

List of Access Actions

Action Notes
Add Entries  
Add Subfolders  
Permanantly Delete Entries Applied on folders only (no effect if directly applied on an entry).
Permanently Delete Subfolders  
Archive Entries  
Archive Subfolders  
Modify Entries Allows: modifying all fields (web client only: modifying password also requires View Entry Password), adding and removing attachments.
Modify Subfolder Names1  
Move Entries Applies to folders only (no effect if directly applied to entry). Must be enabled on source and destination.
Move Subfolders Must be enabled on source and destination.
View Entry Names Required to make an entry visible at all (Web client only: visibility outside of search also requires View Folders on the containing folder).
View Folders  This allows a user to know that a folder exists and see its names.
Request Access  
View Entry Contents

Everything except the password and title. Web client only: users without View Entry Password must also lack Modify Entries (or receive an error).

View Entry Password Web client only: required to allow editing a password.
View Entry History  
View User Access (v7.5.3+) Controls User Access window visibility for users without Grant access on the target entry/folder (those with Grant access can always see the User Access window).
View Entry Offline (v7+) Controls visibility in the KeePass Client's Offline Mode.

Use Via SSO (v7.3.1+) /
Use Via Proxy (v7.2.6-)

Displays SSO Server tab, allows usage of SSO.

Proxy/SSO Server details

Modify SSO Settings (v7.3.1+) / Modify Proxy Settings (v7.2.6-) Proxy/SSO settings are inherited just like access.
View Recorded Sessions Allows viewing of Recorded SSO Sessions for permitted entries
Modify Notification Settings (v7+) Allows attaching/detaching existing Notification Triggers. Attached triggers are inherited just like access.
Modify Comment Settings (v7+) Allows attaching/detaching existing Comment Triggers. Attached triggers are inherited just like access.
Modify PasswordAutoChange Settings (v7.0.16+) Allows creating, editing, and choosing among Credential Hosts. Credential Hosts are inherited like access, with one difference: they can be deleted at any level in the inheritance tree.
Set Block Inheritance Block or Unblock Inheritance
Permit Granting Grant only. Changes all other G access rows so they permit themselves and the corresponding A's to be assigned (rather than only the latter).
This allows a user to Grant access levels which have Grant access rows.

 1 - The ability to rename the Root folder is controlled by the Global Settings role permission:

Move Actions

Move Entries and Move Subfolders behave slightly differently than other access types. In addition to the requirements listed above, the mover needs:

Using Block Inheritance

Be sure to double-check User Access settings prior to setting Block Inheritance.

Typically, the following Access types are inherited:

If you decide to block inheritance on an entry or folder without directly re-adding these access types, you will then lose the ability to perform these actions.

Explanation: The listed access types apply to the entry or folder they are set on.

Restoring Inheritance

By default admins can restore inheritance if they have the following permissions on the object (default setting):

Steps - to create a "Restore Inheritance" access level:

  1. In the web client navigate to: Access Levels tab.
  2. Click Add New Access Level to create a custom access level
  3. Add the permissions (mentioned above)
    • Set Block Inheritance: Action = True, and Grant = True
    • Set Permit Granting: Grant = True

Only provide this Access to a trusted user/role, e.g. to admin.

It is also possible to make this access only available upon request, using the Request-Approve workflow.