SIGNALS Docs
Reader View

Admin Panel

The admin hub — the six areas with a link to every admin page, the admin sheet and its search, how to reach admin, access control, and settings storage.

Overview

The admin panel lets administrators and owners manage system configuration, users, and access control. Access it at /admin or via the Admin link in the user menu.

The admin home and configuration pages require the is_owner flag or membership of the keyed Administrator role. Delegated operations pages use their own permissions, so a non-admin can open the pages they are allowed to use.

Admin has six areas. The admin home, the admin nav and admin search all list the same areas in the same order, and this page follows them too:

You only see the pages your permissions allow, and every page you are shown opens for you. An area with no pages you can open is left out. Facilities needs both settings.view and facilities.view. System Health, Infrastructure, Updates and the Integrations Monitoring tab are self-hosted only and do not appear on Signals Cloud. Imports appears only when the imports feature is on. Admin search finds pages and the tabs inside them by name. Privacy Operations and Merge recommendations open to anyone with their permissions, even without admin access: a privacy officer or data steward sees only those pages in admin.

Finance runbooks — reconciliation, billing-run recovery and multi-currency audits — are in Finance operations. Webhooks are managed in the API console, Workflows and Plugins open from Extensions, and the communication log is a tab on Notifications.

Every admin page opens as a sheet raised over the app. The app's top bar stays visible behind it but is dimmed and cannot be used, so it is clear you are in admin rather than in the app. The sheet has its own frame and a bar along the top with:

  • Admin and your company name
  • Search admin — opens admin search
  • Your settings | Admin — switches between your personal settings and company administration; only users with admin access see this switcher
  • Back to app — closes admin and returns to the last app page you came from, even after switching between Admin and Your settings (or the dashboard if you opened a sheet directly)

Below the bar, the admin nav lists Overview and then one section per area. The area holding the page you are on is open and the page is highlighted. Open or close other areas as you like; admin remembers which ones you opened. Links use wire:navigate, so moving between admin pages does not reload the whole page.

Searching admin

Press / on any admin page (outside a text field), or select Search admin, to open admin search. Type part of a page name, an area, or a word from its description; results are grouped by area and a page whose name starts with what you typed comes first. Tabs inside a page are listed too and open straight on that tab. Use the arrow keys to move, Enter to open, and Esc to close. In Your settings, / opens settings search. Elsewhere in Signals, / opens the command palette. ⌘K opens the palette throughout the app.

On a phone

On a phone the sheet fills the screen below the top bar. Select Admin menu in the sheet bar to open the admin nav over the page; select a page, the close button or press Esc to close it. The search and close buttons in the bar are icons.

The document template editor uses the full width of the sheet and has no admin nav.

Accessing the Admin Panel

There are three ways to reach admin:

  • User menu — click your avatar in the top-right header, then click Admin
  • Area switcher — both sheet bars offer Your settings | Admin to users with admin access. On a phone, it is at the foot of the sheet menu
  • Direct URL — navigate to /admin, the Admin home. It leads with admin search and a row of pages you opened recently (or a Start here set the first time), then one card per area with its pages and a page count

Access Control

Admin configuration pages are protected by the EnsureAdmin middleware, which checks that the authenticated user has is_owner set to true or holds the keyed Administrator role. The middleware is registered as the admin alias and applied to configuration routes alongside setup, authentication, active-user, 2FA and session-timeout middleware.

// Route middleware stack
['signals.setup-complete', 'auth', 'signals.active-user', '2fa', 'admin', 'signals.session-timeout']

Individual actions within the admin panel are further protected by gate checks using the resource.action permission pattern (e.g. users.invite, roles.manage, settings.manage). The account owner bypasses all permission checks via a Gate::before callback.

Relationship reviews

System → Relationship reviews opens the paginated queue of pending relationship evidence without an existing account endpoint. It requires admin access and accounts.view; only operators with accounts.edit can dismiss a review. Inspect the retained IDs, intent and full evidence, then supply a reason and explicit confirmation. Submission rechecks the queue scope and permissions, preserves the evidence and records an immutable disposition receipt. Archived accounts count as existing, so their reviews are excluded. Reviews with an existing endpoint remain on that account's Relationships tab. See Account data repair for the review workflow and global API.

Settings Storage

All admin panel settings are stored in the database via the settings() helper and are cached indefinitely with automatic invalidation on write. Settings follow the group.key naming convention:

// Reading settings
$companyName = settings('company.name');
$isStockEnabled = settings('modules.stock');

// Writing settings
settings()->set('modules.stock', true, 'boolean');
settings()->setMany([
    'company.name' => 'Acme Rentals',
    'company.timezone' => 'Europe/London',
]);

Note

Never use env() or config() for user-configurable values. Always use settings().

Stable Settings Groups

The generic settings API and the corresponding admin forms expose these stable groups. API clients should send partial updates under settings; omitted keys retain their existing values.

Group Keys Admin surface Setup-wizard decision
api rate_limit, rate_limit_unauthenticated, token_expiration_days, require_idempotency_key API Tokens N/A — secure defaults apply until an administrator sets runtime API policy.
availability resolution, snapshot_horizon_past_days, snapshot_horizon_future_days, demand_date_source, release_point, default_turnaround_hours, overdue_check_interval, shortage_acknowledgement_required, shortage_notification_roles, overbooking_approval_required, shortage_warnings_at_quote, daily_summary_retention_years, event_log_retention_months, async_threshold_catalogue_items, recalculation_lock_timeout_ms Scheduling N/A — these values require operational demand and retention decisions.
branding primary_colour, accent_colour, secondary_colour, tertiary_colour, logo_path, logo_has_transparency Branding Configured by the palette and logo setup steps.
company name, timezone, date_format, date_format_php, date_format_js, time_format, time_format_php, fiscal_year_start, base_currency Company Details Configured from company identity and localisation setup inputs.
pricing rounding_direction Finance N/A — the safe half_up default can be changed after installation.
rentals number_pad, number_scope, max_versions, max_alternatives, quote_expiry_warning_days Scheduling N/A — lifecycle limits are post-install operational policy; the numbering keys are migration inputs.
security password_min_length, password_require_uppercase, password_require_number, password_require_special, session_timeout, max_login_attempts, lockout_duration, require_2fa_admin, require_2fa_all, sso_enforced_roles, magic_link_enabled Security N/A — setup provisions the owner before organisation-wide access policy is chosen.
stock_checks close_mode, auto_write_off_missing, blind_count_default, require_supervisor_signoff Scheduling N/A — stock-count policy depends on the warehouse process.
tax unresolved_zone_fallback, default_item_tax_code_id Finance N/A — setup seeds references; finance chooses fallback and catalogue defaults.
workflows max_delay_days, max_chain_depth Scheduling N/A — safe limits apply until workflows are authored.

GET /api/v1/settings, GET /api/v1/settings/{group}, and PUT /api/v1/settings/{group} publish named OpenAPI schemas for these groups. Writes require settings.manage plus the settings:write token ability; reads accept settings:read or the least-privilege settings:read:{group} ability.

Administrator role and API changes

The built-in Admin role has been renamed in place to Administrator, preserving its ID and assignments. A conflicting custom role is renamed to Administrator (custom N). Send roles: ["Administrator"] when assigning the role through the users API; the former built-in name Admin returns 422.

is_admin is deprecated and read-only. It reports Administrator-role membership, ignores the stored database flag, and is false for an owner without that role. Sending is_admin on user creation or update returns 422. Use roles and is_owner to interpret access. filter[is_admin][eq] remains available and filters by role membership.