Skip to main content

Administration: Workspace settings overview

Written by amaise Support

The workspace settings are the administration interface of your workspace. You reach them via the menu at the top right under «Settings». Which areas you see there depends on your role, your permissions, and the features enabled for the workspace — this article gives you the overview.

Who sees the settings

Access to the settings is reserved for administrators:

  • Workspace administrator (tenant:admin) — manages their own workspace: users, roles (read-only), features, reporting, and the organization page.

  • Technical administrator (tenant:tech) — manages settings, integrations, reporting, and users, but has no access to case content.

Basic users and external users do not see the settings.

The areas

The settings are organized into several areas. Not every area is visible for every workspace — some depend on an enabled feature:

  • General — the workspace details (name, URL, data region, language, time zone). Read-only for you: they are changed by amaise.

  • Security — the IP allow list and the role overview.

  • Features — your workspace's configurable templates and defaults (export templates, notebook templates, annotations, default views, and more).

  • Integration — status and credentials of the integration agent (only with the integration enabled).

  • Document mapping — the mapping of external-system keys to storages and document types (only with the integration enabled).

  • Users — your workspace's user management.

  • Reporting and Audit log — analyses and the event log.

What only amaise manages

Some details and features are deliberately managed by amaise and are only visible to you, not editable — for example the basic workspace details, the branding (logo, icon, primary color), and the enablement of individual features. If you want to change something here, contact amaise Support.

Note: Some cards in the settings only appear for amaise Support. If a setting described in this article is missing for you, it is either not enabled for your role or managed by amaise.

Did this answer your question?