Folder Permissions

Control who can view, edit, share, and manage a folder, with inherited access and exceptions clearly visible. This example brings Access and Members together so content and product teams can find the next task without losing context.

It includes representative records such as Product team can edit and Finance can view. Use the screenshot to study the layout, then adapt its components and product states to your own design system.

Folder Permissions
Use this template in Figr

Template facts

Screen

Settings

Primary action

Add member

Pattern

Settings

State

Default, loading, empty, error, permission, success

Design system

Configurable product UI theme

What this screen helps users do

Product teams need to add member while keeping members, editors and exceptions visible. The interface should show what changed and who should act next.

Key elements

  • Main workspace: Access gives users an obvious place to start.
  • Supporting view: Members keeps the related context close.
  • Primary action: Add member stays visible when people need it.
  • First signal: Members shows a useful value (24).
  • Second signal: Editors gives additional context (8).
  • Sample record: Product team can edit.
  • Next record: Finance can view.

States worth designing

  • Default preferences: say what changed, protect progress, and offer a clear next step.
  • Unsaved changes: say what changed, protect progress, and offer a clear next step.
  • Policy blocks edit: say what changed, protect progress, and offer a clear next step.
  • Changes applied: say what changed, protect progress, and offer a clear next step.
  • Restricted settings: say what changed, protect progress, and offer a clear next step.
  • Connectivity interrupted: say what changed, protect progress, and offer a clear next step.

Where this screen sits in the flow

Access → Members → Add member → Review outcome

Patterns used

Settings, Access, Members, contextual actions, error recovery

Why these choices work

Separate safe everyday choices from risky changes, show who can edit them, and confirm irreversible actions.

Pay attention to access and members. People need to distinguish Product team can edit from Finance can view. Keep members visible, especially when a record changes owner or status.

Before this screen reaches handoff, verify keyboard focus, empty and permission states, and what happens after someone chooses “Add member”. Make error recovery as clear as the happy path.

Related screen examples to explore next: Template Gallery, Archive & Restore, Editorial Review.

Start from this in Figr

Design a folder permissions screen inside our existing product. Use our current components, tokens and content language. Include Access and Members views, credible records like Product team can edit, and a clear “Add member” action. Use our product permissions and show loading, empty, error and success states. Keep the output editable in Figma.

Open Figr