Build organization settings

Compose organization settings, a team permission matrix and notification preferences with explicit save and review states.

Organization settings page

Edit organization identity, regional preferences, and session settings with a saved summary.

Organization profile

Organization nameWorkspace address

Time zoneSession duration

Workspace identity

Northstar Studio

fieldbook.local/northstar

Your display name appears on invitations and project activity.

Interactive example with illustrative data. Your application supplies the connected services.

Components in this recipe

2878Organization settings pagePagesEdit organization identity, regional preferences, and session settings with a saved summary.

2899Team permission matrixData displayCompare role permissions and edit project access in an explicit permission grid.

2876Notification preferencesFormsChoose delivery channels for workspace events and save a readable preference summary.

Build it yourself

Load organization settings into a local draft. Submit changes through your application and show validation errors beside the relevant fields.
Place the permission matrix in a separate section. Review role changes before committing them and enforce access on every server request.
Keep notification preferences scoped to the person or organization they affect. Persist successful changes and retain a failed draft for retry.

Build with your agent

A ready-to-use task for your connected coding agent.

Build organization settings

Use the Fieldbook MCP tools search_components and get_component. Select the framework already used by this project. Inspect access requirements and the returned props before editing.

Components: organization-settings-page, team-permission-matrix, notification-preferences.

Load organization settings into a local draft. Submit changes through your application and show validation errors beside the relevant fields.

Place the permission matrix in a separate section. Review role changes before committing them and enforce access on every server request.

Keep notification preferences scoped to the person or organization they affect. Persist successful changes and retain a failed draft for retry.

The interface expresses permissions but does not enforce them. Your backend validates ownership, applies policy and records settings changes.

Test read-only access, unsaved edits, failed saves and long organization names. A successful save should be announced without moving focus unexpectedly.

Preserve the project's styling conventions. Replace illustrative data with application inputs, add meaningful checks, and report integration work that remains.

Members only

Set up MCP Included with Pro

Connect your application

The interface expresses permissions but does not enforce them. Your backend validates ownership, applies policy and records settings changes.

Verify the result

Test read-only access, unsaved edits, failed saves and long organization names. A successful save should be announced without moving focus unexpectedly.