RobbclanTenant AI / Organization & AI controls
Choose how your organization works with AI.
Connect tenant identity, employee directories, shared context and model routes. Give supported agent work an organization behind it.
An organization behind every agent task.
Connect your company identity, employee directory, shared context and model routes. Keep supported agent work inside the tenant’s permissions and source access.
Connect identity
Test the tenant’s company sign-in connection and configure a supported employee directory.
Review authority
Preview exact employee mappings, group roles and account removals before activation.
Run supported work
Connected agents use granted tools with tenant context, model routing and directory lookup where authorized.
Identity and model infrastructure for agent work.
Google Workspace and Keycloak
Each tenant can connect its own supported directory to its tested sign-in configuration. Setup requires that tenant’s authorized directory credential.
Central employee lifecycle
Configured source identity, group roles and enabled status govern managed employee accounts. Review and approve the migration first.
Agent employee lookup
Agents can find work profiles and check synchronization status through read-only tenant-scoped tools. Directory administration remains separate.
Cloud and private models
Choose supported cloud routes or approved private connections. High-security routes have no cloud fallback.
Context and reporting
Keep shared context, routing settings and role-appropriate reporting in the tenant administration area.
Tenant identity and directory setup require an administrator. Live Google Workspace access is validated per tenant; OAuth sign-in alone does not supply directory-management permission. Model routing applies to supported platform tasks.
Give agent work the right foundation.
Available to authorized organization administrators.