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

Go to Settings > User Groups. The Ask D-Tools Access panel sits on that page and shows how many Office users your company has. Click Manage user access to open the list.

Only Office users. Field users are not included and cannot be given access from this screen.

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

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

They are linked, in one direction:

Each column header has an All on / All off control if you want to set every Office user at once.

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

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

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

This is the important part: 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 does not touch any of their other permissions, and adding someone does not widen what they can see.

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

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