Skip to main content

Ask D-Tools: Managing access for your team

How administrators control which users can use Ask D-Tools, and how to enable external connections

Written by Amy Blanton

Access to Ask D-Tools is managed by your company's administrators, separately from your existing user groups and roles.

Who can manage access

Any Office user whose user group has the Manage Account and Subscription permission. It's the user group that counts, not the job title. If you're an admin by role but your user group doesn't include this permission, you won't be able to manage Ask D-Tools access.

Ask D-Tools is already part of your D-Tools Cloud subscription, so there's nothing to request from D-Tools.

Where to find it

Go to Settings > Account > Users & Permissions. The Ask D-Tools Access panel is on that page and shows how many Office users your company has. Click Manage user access to open the list.

Don't see the panel? Check that your user group has Manage Account and Subscription. If it does and the panel still isn't there, ask another administrator to turn on Base Access for you. We're fixing an issue where the panel is hidden from administrators whose own Base Access is off.

Who appears in the list

Only Office users. Field users aren't included and can't be given access from this screen.

Each row shows the user's name, email, and an Inactive marker if their account isn't active.

Use the search box to filter by name or email. Long lists are paginated.

The two toggles

Toggle

What it grants

Base Access

Ask D-Tools chat inside D-Tools Cloud, plus Agent API access

MCP Access

External connections, such as using Ask D-Tools from another AI assistant

They're linked, in one direction:

  • MCP Access requires Base Access. Granting MCP to a user who doesn't have Base Access grants both.

  • Turning Base Access off also removes MCP Access.

Each column header has an All on / All off control for setting every Office user at once.

All off includes you. Turning Base Access to All off removes your own access too. If you only want to exclude certain people, turn them off one at a time.

Who starts with access

When Ask D-Tools was first turned on for your company, every Office user at that time was given Base Access.

Office users added after that start with Base Access off. When you invite someone new, open Manage user access and turn them on if they should have it.

MCP Access is always off by default and has to be turned on deliberately, one person at a time. That's intentional. Connecting an external assistant is a bigger decision than using the chat inside D-Tools Cloud, so it's never granted automatically.

Narrowing access

If you don't want everyone to have it, turn Base Access off for the users you want to exclude. You don't need to change their user group, role, or any other permission.

Ask D-Tools membership is additive. It sits alongside a user's existing user group rather than replacing it. Removing someone from Ask D-Tools doesn't touch any of their other permissions, and adding someone doesn't widen what they can see.

Removing access

Turn Base Access off and the user immediately loses Ask D-Tools chat, Agent API access, and any external connection. There's nothing else to clean up.

What users can see

Ask D-Tools never shows a user data they couldn't already reach in D-Tools Cloud. Answers are scoped to that person's own permissions, so giving someone access to Ask D-Tools doesn't give them access to anything new. If part of an answer needed data they can't view, Ask D-Tools says so rather than filling in the gap.

Did this answer your question?