Skip to content
Free$1 of credit for every new organization
All articles

Product

Teams on Usefully: organizations, members and roles

Share one balance, one set of keys and one view of usage with your team, and give each person only the access they need.

· 3 min read · Usefully team


Most AI projects stop being one person's side project quickly. Someone needs to see the bill, someone else needs a key for staging, and a teammate wants to check why a request failed. Organizations are how Usefully handles that: one balance, one set of API keys and one usage history, shared by the people you invite, each with a role.

What belongs to an organization

  • Credit balance. Every key in the organization draws on it. Top-ups, invoices and refunds belong to the organization.
  • API keys, each with its own limits.
  • Logs and usage: every request with its model, provider, tokens, cost and latency, and spend by day, key and model.
  • Alerts, such as low-balance alerts.
  • Members and their roles.

You can belong to more than one organization, for example one per company or client, and switch between them in the dashboard. Balances and keys never mix.

Roles

Each member has one role. Pick the smallest one that lets them do their job:

  • Owner: everything, including deleting the organization and managing other owners.
  • Admin: manage members, keys and billing.
  • Developer: create and revoke API keys and use the playground. The right role for most engineers.
  • Billing: buy credits and manage billing settings. Good for finance, without access to keys.
  • Viewer: see usage, logs and settings, but change nothing. Useful for managers and support staff.

Inviting people

Admins and owners add people from the Members page and choose a role for each. Roles can be changed later, and a removed member loses access to the organization's dashboard.

Keys outlive people, so plan for it

API keys belong to the organization, not to the person who created them. When someone leaves, their dashboard access ends when you remove them, but any key they created keeps working until it's revoked. Two habits keep that safe:

  1. 1Name keys by purpose, not by person: billing-worker-prod survives a team change; alice-key raises questions.
  2. 2Give personal development keys a small daily spend limit, and revoke them when the person leaves.

A typical small-team setup

  • Two owners, so the organization is never locked out if one person is away.
  • Engineers as developers, each with a personal key for local work.
  • Production and staging keys created by an admin, with limits, stored in your secret manager.
  • The person who pays invoices as billing.
  • Everyone else who just needs to look, as viewers.

Separate organizations for separate budgets

If two projects need hard budget separation, such as client work billed back to different customers, use two organizations rather than two keys. Each has its own balance, invoices and usage, so there's nothing to untangle at the end of the month.

If you're not sure which role someone needs, start with viewer and upgrade when they ask. It's easier to grant access than to find out later who changed a setting. Review the member list now and then, too, especially after team changes, and remove anyone who no longer needs access.

Organizations are free, and your first one gets $1 of free credit. Create one, or write to support@usefully.info if you need help moving a team over.

More articles

Get started

Your first request is five minutes away.

  • $1 of free credit to start
  • No card, no subscription
  • Keep the SDK you already use
  • Real people at support@usefully.info
Teams on Usefully: organizations, members and roles · Usefully