Enterprise Workspace Guide

Enterprise Workspace lets employees sign in to Nbility with separate accounts, create their own enterprise API keys, and have API usage billed centrally to the enterprise Owner. This guide covers workspace setup, invitations, key management, usage, and logs.

How Enterprise Workspace works

After joining an enterprise workspace:

• The Owner manages the enterprise wallet, members, key policy, and overall usage.
• Every employee signs in with their own Nbility account. The Owner's credentials never need to be shared.
• Every member can create and manage their own enterprise keys.
• The Owner and administrators can view organization-wide usage. Regular members can view only their own keys, usage, and request logs.
• Enterprise keys and personal keys remain separate. They are never migrated or combined automatically.

All calls made with enterprise keys are charged to the Owner's existing wallet balance. Enterprise Workspace V1 does not share subscriptions and does not include seat billing, departments, cost centers, or multi-level organizations.

Roles and permissions

The Owner is the workspace's only billing owner. The current version does not support Owner transfer or membership in multiple enterprise workspaces.

Before you start

Prepare the following:

1. A Nbility account that will become the enterprise Owner.
2. A sign-in email address for each employee.
3. Enough available balance in the Owner's wallet.
4. The preferred per-member key limit and per-key quota limit.

Open the Nbility Console to begin.

Create a workspace as the Owner

1. Sign in to Nbility with the Owner account.
2. Select the avatar in the lower-left corner of the console, then select Create Enterprise Workspace.
3. Enter the enterprise name and submit the form.
4. After creation, Enterprise Workspace appears in the sidebar and the creation item disappears from the avatar menu.
5. Open Enterprise Workspace → Settings, review the enterprise key policy, and save it.

A new workspace uses these defaults:

• Up to 50 non-deleted enterprise keys per member.
• A default quota of US$100 for each new key.
• A maximum quota of US$1,000 for a single key.
• Unlimited-quota keys are disabled by default.

The Owner can change the enterprise name, per-member key limit, default quota for new keys, maximum quota for one key, and whether unlimited-quota keys are allowed.

If a new policy conflicts with an existing key, such as reducing the maximum below a key's current quota, the system rejects the change. Update the affected keys before changing the policy.

Invite employees

1. The Owner or an administrator opens Enterprise Workspace → Members.
2. Select Invite Member.
3. Enter the employee's email address and choose the Administrator or Member role.
4. Create the invitation, copy the invitation link immediately, and send it through an approved internal channel.

Invitation rules:

• An invitation link expires after 7 days and can be used only once.
• The credential in the link is shown only when the invitation is created. It cannot be viewed again in the invitation list.
• The email address on the employee's signed-in account must match the invited email address.
• The current version does not send invitation emails automatically. The Owner or an administrator must send the link.

You can invite an employee who has not registered yet. After registering and signing in, the employee must return to the original invitation link to continue.

Accept an invitation as an employee

1. Open the invitation link sent by the enterprise administrator.
2. If needed, register or sign in to Nbility with the invited email address.
3. Verify the enterprise name, invited email, and role shown on the page.
4. Select Join Enterprise Workspace.
5. After joining, Enterprise Workspace appears in the console sidebar.

If the page reports an email mismatch, sign out and use the invited email address. An account that already belongs to another enterprise workspace cannot accept a new invitation.

Create and use enterprise keys

Create a key

1. Open Enterprise Workspace → Keys.
2. Select Create Key.
3. Enter a key name and select at least one API group currently available to the Owner. Multiple groups are tried in the selected order; Auto group cannot be combined with another group.
4. Optionally set a business group, expiration, key quota, period quota, model limits, and allowed IPs. The model picker contains only models covered by the Owner's currently available enterprise groups.
5. If the Owner allows unlimited-quota keys, you can select Unlimited quota. Batch-created keys receive random name suffixes and still count toward the per-member key limit.
6. Save and copy the key secret, then store it in an enterprise-approved password manager or secret manager. Secrets are shown only immediately after creation or when explicitly revealed.

The key quota limits how much the individual key can use. The Owner's wallet balance limits how much the enterprise can actually pay. A request can succeed only while both conditions are true:

The enterprise key has quota remaining, and the Owner's wallet has balance remaining.

Unlimited quota removes only the per-key quota limit. The key remains limited by the Owner's wallet balance.

Call the API

Enterprise keys use the same API authentication as regular Nbility API keys. Replace the placeholders in this OpenAI-compatible example:

curl https://api.nbility.ai/v1/chat/completions \
  -H "Authorization: Bearer <enterprise-key>" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "<model-name>",
    "messages": [
      {"role": "user", "content": "Hello"}
    ]
  }'

Never place a real key in a public repository, ticket, chat screenshot, or frontend page. If a key may have leaked, disable or delete it immediately and create a replacement.

View quota, analytics, and logs

Enterprise Workspace contains these pages:

• Overview: wallet or key balance, usage over the last 7/30/90 days, request count, top keys, and recent management activity.
• Keys: creator, API group, business group, status, remaining/used quota, and expiration, plus reveal, full-configuration editing, enable, disable, and delete actions.
• Logs: the same request fields and details as personal logs, with filters for key, log type, model, API group, business group, request ID, upstream request ID, status code, error text, and time range.
• Members: members, roles, key counts, and invitation status.
• Settings: enterprise name and enterprise key policy. This page is visible only to the Owner.

The Owner and administrators can view organization-wide analytics, all enterprise keys, and organization-wide logs. Regular members can view only keys they created and their own analytics and logs. Administrators cannot reveal other members' key secrets; the Owner can reveal them when necessary.

Employee departure or workspace exit

When an employee leaves the organization, the Owner or an administrator should remove them promptly from Enterprise Workspace → Members. Administrators and regular members can also leave the workspace themselves.

After a member is removed or leaves:

• Enterprise keys created by that member are disabled immediately.
• The member can no longer access enterprise data.
• Historical request logs and management audit records are retained.
• Rejoining later does not automatically re-enable old keys.

The Owner cannot leave the workspace. The current version also does not support Owner transfer or self-service workspace deletion. Contact Nbility support if either is required.

Frequently asked questions

Must every employee register an account?

Yes. Every employee signs in with their own Nbility account. Employees must not share the Owner account.

Whose balance does an enterprise key use?

All enterprise-key usage is charged to the Owner's existing wallet balance. Employees do not fund enterprise keys separately.

Are personal balances and personal keys affected?

No. Personal wallets, personal keys, and enterprise keys remain separate. Joining an enterprise does not migrate or modify personal keys.

Can the enterprise share the Owner's subscription?

No. Subscription sharing is not supported in the current version. Enterprise keys use the Owner's pay-as-you-go wallet balance.

Why can an employee not accept an invitation?

Check that the signed-in email matches the invited email, the invitation has not expired or already been used, and the account does not already belong to another enterprise workspace.

Why does a request fail when the key still has quota?

Check the Owner's wallet balance, key status, key expiration, and enterprise policy. Remaining key quota does not guarantee that the Owner's wallet has available balance.

Can a deleted key be restored?

No. Disable a key when the interruption is temporary, and delete it only when it is no longer needed.

How many enterprise keys can an employee create?

The Owner configures this limit in Enterprise Settings. Disabled but non-deleted keys still count toward the limit.

Security recommendations

• Protect the Owner account with the strongest sign-in methods available on the platform, and never share the account.
• Give the Administrator role only to people who need to manage members and enterprise keys.
• Send invitation links and API keys only through enterprise-approved secure channels.
• Create separate, clearly named keys for different employees and purposes, with suitable quotas and expiration times.
• Review enterprise logs, key status, and the member list regularly. Disable a key immediately when usage looks suspicious.
• Update roles or remove members promptly after employment or responsibility changes.
• Record the request ID when troubleshooting, but never send a complete API key.

Current version limitations

Enterprise Workspace V1 does not support:

• Sharing the Owner's subscription or subscription quota.
• Joining multiple enterprise workspaces with one account.
• Transferring the Owner role.
• Self-service workspace deletion.
• Departments, cost centers, seat billing, or multi-level organizations.