More than a help desk. A little more human. Meet your new workspace
helpdash.
Security and access

Helpful by nature.
Careful with access.

Your support workspace holds real conversations and customer context. Give people and integrations the access their work calls for.

Talk through your requirements
Your workspace
AM
Alex MorganWorkspace member
View ticketsAllowed
Write repliesAllowed
Manage workspaceNot granted
Access follows the role you assign.

Illustrative permission setup

Clear boundaries.
Practical controls.

Product controls you can use when setting up your team, identity provider and connected tools.

Access that follows responsibility.

Roles and granular permissions determine which product areas a member can access and which actions they can take. Authoring, publishing, reporting and workspace administration can be assigned separately.

  • Workspace roles and permissions
  • Separate management and publishing rights
  • Agent groups for ownership and routing

A defined workspace boundary.

Helpdash binds requests to a tenant context and checks the workspace associated with the authenticated user. Customer portal access and operator access use separate authentication guards.

  • Tenant-scoped application data
  • Workspace context enforcement
  • Separate customer and operator authentication

The right way into the workspace.

Two-factor authentication adds another step to operator sign-in. SAML single sign-on and SCIM provisioning support connected identity management where configured.

  • Two-factor authentication and recovery codes
  • SAML single sign-on
  • SCIM user provisioning

Connections with limits of their own.

MCP connector scopes narrow an integration’s access to the permissions of its owner. Static tokens can have an expiry and IP allowlist; tokens can be disabled from the AI connectors settings.

  • Read and per-module write scopes
  • Owner permissions remain the access ceiling
  • Static token expiry, revocation and IP allowlists
Connected AI assistants

Permission to connect
is only the start.

An external assistant’s MCP access must pass the same workspace and permission checks as the operator it represents.

Explore AI connectors
  1. 1

    Resolve the workspace.

    The authenticated connection is bound to its tenant context.

  2. 2

    Check the granted scope.

    Read access and module write scopes define what the connector may request.

  3. 3

    Check the owner’s permissions.

    A connector cannot use a scope to exceed its operator’s rights.

  4. 4

    Record the interaction.

    MCP authentication and tool calls produce audit entries for traceability.

The details
deserve a conversation.

Identity requirements, deployment questions, data handling and procurement checks can vary by team. Share what you need to review and we can work through the specifics.

Contact the Helpdash team

Planning your rollout?

A useful place to begin is your role structure, identity provider and integration inventory. We can help map those requirements to your Helpdash setup.

Explore workspace controls

Open your workspace.

Your team has its own address. Enter its name and we’ll take you there.

.helpdash.io

No workspace yet? Start a free trial

We remember the name on this device so it is filled in next time. Privacy policy