# Organizations & budgets > Roles, members and invites, projects and keys, key spend limits and expiry, the monthly budget, credits and their expiry, payments, status. Source: https://kiln.bricksum.com/docs/en/organizations Everything you do with the API belongs to an organization: keys, usage, credits, budget and rate limits. This page covers how organizations, members, projects and keys fit together, the limits you can set, and how credits and payments work. ## Organizations and roles Signing up creates a personal organization with you as its owner. An organization has exactly one owner and any number of admins and members. Admins manage keys, projects, members, budget and settings; members use the console read-only and cannot issue keys. A personal organization has no member management. Switch the active organization in the console to work on another one you belong to. ## Members and invites Admins invite members by email from Org → Members; a pending invite can be cancelled or resent, and the same address cannot be invited twice. The invitee accepts from the email link after signing in. In a team organization, admins change a member's role, the owner transfers ownership to another member, and any member other than the owner can leave, all from Org → Members. Where a deployment does not support one of these actions yet, the console shows it as coming soon. ## Projects and keys Projects group keys inside an organization; every organization starts with a Default project. Each API key belongs to exactly one project and is created by an admin on the API keys page with just a name. The sk-bk- secret is shown once. Usage is attributed to the key, its project and its organization, so the Usage page can break down by any of them. ## Key limits and lifecycle After creation, an admin can manage a key in four ways. Set a spend limit in USD: requests are rejected once the key's cumulative spend reaches it, and empty means unlimited. Set an expiry date: requests are rejected after the end of that day. Suspend and reactivate it: requests are rejected while suspended. Delete it: revocation is immediate and permanent. The keys list shows spend against the limit and marks expired keys. The status code of each rejection is listed on the Errors page. ## Monthly budget An admin can set a monthly budget in USD on Org → Settings. The console shows a warning banner when the month's spend reaches 80 % of it and a red banner at 100 %. From then on, every API request from the organization is rejected until the month rolls over or the budget is raised. The Errors page lists the status code. No budget means unlimited. ## Rate limits Requests per minute, tokens per minute and concurrent requests are limited per organization. The values are managed by the operations team and shown read-only on Org → Overview. Contact us before a load test that needs more. ## Credits and expiry Credits are prepaid in USD and expire: trial credit 30 days after it is granted, purchased credit 365 days after purchase. The Credits page shows the balance, a ledger of every grant, charge, refund and expiry, and what expires within the next 30 days. The organization owner receives one email when the balance runs low. ## Payments and receipts Where the console offers Top up, you buy credit by card. The charge currency and VAT are set by the payment service and shown on the checkout screen before you pay; today the charge is in KRW, with 10 % VAT on top of the credit amount. The credit you buy is added to your balance in USD. The Payments page lists each payment with its status, amount, VAT, method, receipt link and refund state. Where Top up is marked coming soon, the operator grants credit. Write to contact@bricksum.com. Invoices are not available. ## Status and announcements Service status and 90-day uptime per component are public at https://status.bricksum.com. Maintenance windows and other notices are published as announcements that appear in the console and on the landing page. See also: [Usage & billing](https://kiln.bricksum.com/docs/en/usage-billing) · [Rate limits](https://kiln.bricksum.com/docs/en/rate-limits) · [Errors](https://kiln.bricksum.com/docs/en/errors) · [Console → Organization](https://kiln.bricksum.com/app/org) Note Items marked coming soon in the console are not available through the API either. Only the features the console offers today are available.