Identity & security
Google Workspace reporting on Google Workspace Directory users, groups and devices
Google Workspace Directory is the account directory behind a Google Workspace domain. Administrators manage users, groups, organizational units, admin roles and ChromeOS and mobile devices in the Admin console or through the Admin SDK Directory API. Organizational units decide which policies and services apply to each user.
Google Workspace Directory
Available now: Nexatron answers Google Workspace Directory questions with user-level access that inherits your existing Google Workspace Directory permissions.
Updated
Can Claude, ChatGPT or Copilot access Google Workspace Directory data?
Yes. To connect Claude, ChatGPT or Copilot to Google Workspace Directory, add Nexatron from Claude’s connector directory, or by its MCP server URL in ChatGPT and Copilot. Then connect it in Nexatron. Users sign in with their own Google Workspace Directory account (or your SSO), and Nexatron inherits their existing permissions.
What Google Workspace Directory data a question reads
- Users
- User accounts with primary email, name, organizational unit path, suspended and archived flags, isAdmin, isEnrolledIn2Sv, isEnforcedIn2Sv, last login time and creation time.
- Groups and members
- Groups with email, description and member count, and members with role (owner, manager, member) and type (user, group, external).
- Organizational units
- The OU tree with paths and parent units, which controls policies and service access for users and devices.
- Role assignments
- Admin roles, including Super Admin and custom roles, assigned to users or groups, with scope to the whole customer or an OU.
- ChromeOS and mobile devices
- Managed devices with serial number, model, OS version, status, last sync and assigned user or OU.
Google Workspace Directory questions people ask
- How many active users in each organizational unit are not yet enrolled in 2-step verification?
- Which accounts have not signed in for 90 days and are still active?
- Who currently holds the Super Admin role, and when did each of them last sign in?
- Which groups have external members, and who owns each of those groups?
- How many ChromeOS devices in each OU are running an OS version older than the current stable release?
- How many users were created and how many suspended in each month this year?
Who asks Google Workspace Directory questions
- IT administrators
- Inactive accounts, OU placement and device status, without exporting a user list to a spreadsheet.
- Security and compliance
- 2SV coverage, admin role holders and groups that include people outside the domain.
- People operations
- Joiner and leaver counts and whether departed employees still hold active accounts.
How Nexatron connects to Google Workspace Directory
- API and sign-in
- The Admin SDK Directory API, authorized with OAuth 2.0 for each user under read-only directory scopes.
- User-level access
- Users sign in with their own Google Workspace Directory account (or your SSO), and Nexatron inherits their existing permissions. Users only see data they are already authorized to see.
- Read-only
- Questions only read Google Workspace Directory; asking a question never changes Google Workspace Directory data.
- Setup
- An administrator enables Google Workspace Directory in Nexatron. Users link their own Google Workspace Directory account, or sign in through your SSO, the first time they ask. Queries run in Google Workspace Directory, with no warehouse to load.
Google Workspace Directory in Claude’s connector directory
Nexatron is listed in Claude’s MCP connector directory, so a Claude user can add it without a custom server URL. Its hosted MCP server answers Google Workspace Directory questions for Claude, ChatGPT and Microsoft Copilot with user-level access, and the same governed answer as the Nexatron app. It is Nexatron’s own server, not one published by the vendor.
- Connect Google Workspace Directory to your Nexatron workspace.
- In Claude, add Nexatron from Claude’s connector directory. In ChatGPT or Copilot, add a custom MCP connector with Nexatron’s server URL.
- Sign in with your own Nexatron identity (OAuth 2.1), then ask your Google Workspace Directory questions.
Server URL for a custom connector: https://api.nexatron.io/api/v1/mcp
Google Workspace Directory questions and answers
- How do I report on 2-step verification in Google Workspace?
- The Admin console has a security report showing 2SV enrollment and enforcement per user, and the Directory API exposes isEnrolledIn2Sv and isEnforcedIn2Sv on each user. Grouping those fields by organizational unit shows where enforcement still has gaps.
- Which resources does the Admin SDK Directory API cover for Google Workspace?
- Users, aliases, groups and members, organizational units, admin roles and role assignments, ChromeOS devices, mobile devices, schemas for custom user attributes and domains. Sign-in and audit events come from the separate Reports API in the Admin SDK.
- Who can see the Google Workspace directory?
- Administrators with the right admin privileges see full user records for the OUs their role covers. Regular users can see a limited, domain-shared view of names and emails, controlled by the directory sharing settings in the Admin console.
Try Nexatron with your Google Workspace Directory
Tell us the Google Workspace Directory questions you want answered and who asks them, and we plan the demo around them. Do not include credentials or confidential records.
Google Workspace Directory is a trademark of its owner.