Every team in its own business unit.

Organizations, business units and users

The organization is your company, and the business units in it are teams, product lines, brands or regions. Every user only sees their own scope.

• Platform admins manage everything, including organizations and Data Hub settings
• Organization admins, for example from RevOps, manage business units, connections, approvals and users
• Business unit users, such as your demand gen team or a region's SDRs, work in exactly one business unit
• Access only by invitation link; there's no self-signup

Connect links for tool admins

The admin access to HubSpot, Salesforce or the ad accounts often sits with someone other than you. Instead of trading passwords, you send them a link. They sign in with each vendor or enter an API key, with a short guide under every tool. The link is valid for 1 to 30 days, can be revoked at any time and only replaces a working connection if you explicitly allowed it. The hub reports every replacement.

Connection monitoring

Every morning the Data Hub checks all connections across all business units and spots access that's about to expire. When something's wrong, you get an alert, by email with a ready-made connect link to forward to whoever holds the access. If the problem persists, a reminder follows, and you can opt into an all-clear once it's fixed.

Notifications per organization and business unit

Approvals, connection problems and hit limits go by email, Slack or Microsoft Teams to whoever is responsible. The organization and its business units set up their own channels and pick the events they want. Each level gets its messages in German or English, including a team's own Slack channel.

Usage, packages and quotas

Per business unit and calendar month, the hub counts calls, write actions, errors and Clay usage, as plain numbers. The Usage page shows every business unit in your area, and you export one month, or twelve months per business unit, as CSV. Platform admins create packages with monthly quotas and assign them to business units.

• Warning at 80 and 100 % to the channels that chose “Limits, emergency brake & quotas”
• If you want, the hub refuses further calls at 100 %, with a clear message to the agent
• Read calls keep working when only the write or Clay quota is used up
• Clay credits are read from the account balance once a day

Activity log and Coverage

Every tool call is logged with time, MCP server, tool, success or error and duration. Export the last 30 or 90 days, or everything, as CSV. The Coverage page describes each source in plain language: what an agent can read and change, and where the limits are.