Skip to main content

How to manage access when working with multiple clients

If you’re managing multiple clients in Tresal — for example as an MSSP — what’s the best way to structure user access per client?

Matthias Peeters avatar
Written by Matthias Peeters
Updated over 2 months ago

Recommended approach: one workspace per client

Tresal is built with a multi-workspace model in mind. This means that for each client, you create a separate workspace.

Each workspace is fully isolated — with its own data, assets, users, and configuration.


Example:

Let’s say your company manages 25 clients.

You would create:

  • 25 separate workspaces — one for each client

  • Invite each client’s team members only to their own workspace

This setup allows you to:

  • Keep client environments fully separate

  • Provide clients with direct access to only their own assets and findings

  • Simplify permissions, reporting


🔒 Why workspaces over asset-level access?

Tresal doesn’t require complex asset-level permissioning within a single workspace, because the workspace model already solves that:

  • Each workspace contains only the relevant assets

  • Only users added to that workspace have visibility

  • Everything is logically and securely separated

This ensures a clean and efficient structure for MSSPs and service providers.

🧠 Summary

Use case

Recommended setup

Internal team or single environment

One shared workspace

Multiple clients or tenants

One workspace per client

💬 Need help onboarding multiple clients? Contact [email protected] — we’re happy to help you structure your setup.

Did this answer your question?