Feature: Nested Shared Folders
Keeper's Nested Shared Folders let you organize records the way your teams actually work, with role-based permissions at every level. Access is inherited from the parent folder by default, or fine-tuned for specific subfolders and individual records. Permissions can be assigned to users or teams and provisioned automatically at enterprise scale through directory mapping and SCIM.
In the Keeper Vault, click Create New, then Folder. Pick a location and name it. Sharing comes after the folder exists, so you can set up the structure first and share it when you're ready.
Add subfolders inside any folder, up to five levels deep. Each subfolder can inherit permissions from its parent or define its own.
Add records to a folder from the vault. A record can live in more than one folder at once.
Select a folder or record, click the Share button, then add users or teams and assign role permission levels. Set expiration dates or revoke access at any time.
Build folders and subfolders around teams, projects or clients. Sharing and permissions are managed independently at each level, and the structure scales as the team grows.
Permissions can be inherited from a parent folder, assigned directly to a folder or assigned directly to an individual record. Set one broad policy at the top and make precise exceptions anywhere below it.
Folder roles provide a simple and scalable method of assigning permissions to any managed resource in the vault. Roles cover both folder contents and user management. Roles include Viewer, Share Manager, Content Manager, Content and Share Manager, and Full Manager. Each role maps to a clear set of abilities, so people get exactly the access their role requires and nothing more.
External workloads such as CI/CD pipelines, cloud services and automations access secrets through Keeper Secrets Manager applications, which can be assigned to any Nested Shared Folder with Can Edit or Read Only permissions.
Add users and teams, update permissions, set expiration dates and revoke access from one place. No one can grant permission levels higher than their own.
Nested Shared Folders are fully supported in Keeper's 3rd party integrations such as Sailpoint, ServiceNow, Jira, Slack and other IT tools. Developers can work with folders using the Keeper Commander® CLI, SDKs, Terraform providers and REST API.
Nested Shared Folders offer five roles, each mapped to a clear set of abilities:
Nested Shared Folders are a ground-up rebuild of Keeper's folder, sharing and permissions model, with role-based permissions and inheritance across a five-level hierarchy. Classic folders use Keeper's original sharing model. Each type shows a distinct icon: Nested folders appear solid, Classic folders transparent.
No, they're separate structures and can't be combined within the same hierarchy. Both can run side by side and there's no forced migration, so teams adopt Nested Shared Folders at their own pace.
Content Manager can edit and create records but can't control who has access. Content and Share Manager does both: managing content and managing sharing.
Yes, unless they have direct permissions on those individual records. Folder access and record access are tracked separately, so a direct grant on a record survives removal from the folder.
Access ends automatically on that date, with no manual step. It's built for contractors, time-limited projects and any access that shouldn't outlive its purpose. For a full walkthrough, see the Nested Shared Folders guide.
チャットサポートを利用する場合、Cookie を有効にしてください。
