Manage workspace settings

Workspace administration changes settings for everyone in the current workspace. It is available only to members with workspace administrator permission.

If you are a standard member, ask an administrator to make workspace-wide changes. Personal notification and profile settings remain available to you.

Set organisation context#

Open Administration, then Organisation. Edit the company profile, objectives, and tone of voice. Primary market and categories are read-only here; ask your Signal contact to correct them.

This context helps Signal frame analysis and reports in the language of your business. It guides wording and emphasis; it is not a substitute for factual data or source documents.

Use the verified organisation domain carefully because domain-restricted report links rely on it.

Control external report sharing#

The Organisation page also controls whether members can create public external report links and how long new links remain valid.

Enable public links only when the workspace has a genuine need to share reports with recipients who cannot sign in. Prefer domain-restricted links when the audience belongs to a known organisation.

Changing the default expiry affects new links, not links already created. Review and revoke existing links from the report that owns them.

Apply report branding#

Open Administration, then Branding to set the accent colours and logo used in generated reports. Branding does not change the Signal application interface.

Use the live preview to check that chart series remain distinguishable and that the logo is readable. Save the branding after changing colours, uploading or fetching a logo, removing a logo, or resetting to Signal defaults.

Members can still choose Signal, workspace, or high-contrast theme while viewing and exporting an individual report. That viewing choice does not change the saved workspace branding.

Manage workspace users#

Use the Users page to review access and roles available to the workspace. Grant administrator permission only to people who need to change shared configuration or approve governed data changes.

Remove access promptly when a person leaves the team or no longer needs the workspace. Review ownership of recurring Tasks, integrations, and shared work as part of offboarding.

Connect team notifications#

Open Administration, then Notifications to connect supported Slack or Microsoft Teams destinations using an incoming webhook.

Give each destination a clear name, send a test, and select the events it should receive. Route alerts by audience: an operations channel may need data-load and Task failures, while a commercial channel may only need published reports and requests for input.

Pause a destination when it is temporarily noisy or under maintenance. Replace its webhook if tests fail, and remove it when the channel is retired.