Data Access Control

Give each team the data access it needs—and no more

Guance Data Access Control combines workspace membership, roles, data rules, field masking, and authorised cross-workspace access. Platform administrators can support shared investigations while preserving boundaries for logs, RUM, security, audit, and business data.

Give each team the data access it needs—and no more

What Data Access Control helps you solve

Let teams collaborate without making every dataset universally visible

A shared platform needs more than account-level access. Define who can query which data, how sensitive fields appear, and when another workspace receives explicit access to selected context.

Start with the query boundary: who should see which records?
Use roles, workspaces, and data-access rules to limit the data different members can query. Apply the model to logs, experience, audit, security, and business datasets according to ownership and classification.
View documentation
Start with the query boundary: who should see which records?
Mask sensitive fields without discarding all diagnostic value
Mask sensitive fields without discarding all diagnostic value
Apply built-in or custom regular-expression rules to selected phone numbers, identity values, accounts, keys, tokens, IP addresses, or business fields. Review each rule against false positives, operational usefulness, and authorised exceptions.
View documentation
Use explicit cross-workspace authorisation for shared investigations
Authorise selected data for another workspace while keeping the source workspace boundary intact. This supports platform, group, and multi-business investigations without treating all telemetry as globally shared.
View documentation
Use explicit cross-workspace authorisation for shared investigations

Frequently asked questions

When is observability Data Access Control needed?

It is needed when one platform serves multiple teams, business lines, contractors, or partners and not every user should query every dataset or view every sensitive field.

How are access control and data masking different?

Access control decides who can query a dataset or resource. Masking changes how selected field values appear. Combining both reduces exposure while preserving approved collaboration.

Can teams share data across workspaces?

Guance supports documented cross-workspace authorisation patterns for selected data. Administrators should define source ownership, recipient scope, sensitive-field handling, and review procedures before enabling access.

Explore more

Resources and further reading

Choose the next step from product documentation, related solutions, and technical guidance.

Related reading

Product guides, troubleshooting workflows, and technical best practices

Build a queryable log investigation workflow

Build a queryable log investigation workflow

Structure log fields and keep service, host, status, duration, and trace context available for analysis.

Product features
Plan an enterprise log management architecture

Plan an enterprise log management architecture

Connect collection, processing, storage, search, access, and investigation as one governed data path.

Best practices
Use Pipeline to improve telemetry quality

Use Pipeline to improve telemetry quality

Parse, normalize, filter, and protect data before downstream teams depend on it.

Product features
Compare managed log analytics with an ELK workflow

Compare managed log analytics with an ELK workflow

Review the operational questions involved in collection, storage, querying, visualisation, and ownership.

Industry insight

Continue into sensitive-data and enterprise governance

Explore sensitive-data scanning, enterprise management, logs, documentation, and pricing.

Get started > View documentation > View pricing >