Administration
The Administration module allows authorised users to configure the core functionality, appearance, and data structures of the MuseumStack instance.
:::note [TODO: Add Screenshot of Administration Overview] :::
General Settings
Section titled “General Settings”Manage your museum’s identity, contact information, and public-facing profile.
- Museum Name & Slug: Configures how your museum appears in the application and its URL.
- Contact Details: Publicly accessible email and phone for visitor enquiries.
:::note [TODO: Add Screenshot of General Settings Page] :::
Users & Roles
Section titled “Users & Roles”Manage who can access the system and what they can do.
- Inviting Users: Send email invites to new staff members.
- Role Assignment: Assign pre-defined roles (e.g., Curator, Admin, Researcher) to control feature access.
- Permissions: Each role is a collection of specific permissions.
:::tip [RESERVED: Placeholder for detailed Role/Permission matrix or custom role creation] :::
Collection Setup
Section titled “Collection Setup”Define the data structure for your catalogue.
- Custom Fields: Add entity-specific fields (Item, Accession, Contact) to capture unique metadata.
- Form Layouts: Use the Form Builder to arrange fields for different departments or data entry workflows.
- Vocabulary Management: Maintain controlled terms for dropdowns and authority-controlled fields.
:::note [TODO: Add Screenshot of Form Layout Builder] :::
Policies & Compliance
Section titled “Policies & Compliance”Configure systematic rules and legal requirements.
- Access Policies: Define who can see sensitive records.
- Audit Logs: Review chronological activity logs (System Admin only).
Permissions Required
Section titled “Permissions Required”Administrative access is highly restricted. The following permissions are required:
- Museum Admin (
museum_read,museum_update): Grants access to general settings and policies. - User Management (
users_read,users_manage): Required to invite staff and assign roles. - Collection Configuration (
collections_setup_read,collections_setup_manage): Allows modification of fields and layouts. - System Admin (
system_admin): Highest level; required for audit logs and system-wide migrations.