Permissions & security

Manage access to Dawn and establish safe working practices.

Good analytics governance combines platform permissions with clear team practices. Give people the access they need to do their work, keep sensitive data deliberate, and review important outputs before they are used.

Manage access deliberately

Use organisation and workspace access to keep work visible to the right people. When setting up a workspace, decide:

  • Who should be able to view its data and assets
  • Who can create or change pipelines, dashboards, reports, and jobs
  • Who owns important datasets and metric definitions
  • How access is reviewed when someone changes role or leaves the team

Use the smallest practical level of access for sensitive data. Create a separate workspace when a group needs a different access boundary.

Protect credentials and sensitive data

Store integration credentials in Secrets rather than in a dataset, pipeline, report, conversation, or job instruction. Share only the data required for the task, and follow your organisation's policies for personal, financial, health, or other sensitive information.

Before connecting a new source, confirm that the intended users are allowed to access it and that the retention, residency, and contractual requirements are understood.

Build review into important workflows

For reports, dashboards, and jobs that influence material decisions:

  1. Name an accountable owner.
  2. Document the source data and important metric definitions.
  3. Validate a sample of outputs against the source.
  4. Review changes to logic, instructions, and schedules.
  5. Define what should happen when data is missing or a result looks unusual.

Report a concern

If you believe access, data, or an integration has been configured incorrectly, stop using the affected asset and contact your Dawn administrator or TrueState support. Include the workspace, affected asset, and a short description of the issue; do not include credentials in the message.