organizations
organizations are the account unit in crawlbrulee. everything hangs off the org, not the individual user: api tokens are org-scoped, and every member draws from the same credit pool, rate limits, and concurrency — see token scoping.
a default organization is created for you at signup. you manage organizations — members, roles, billing, deletion — from the dashboard ; there are no public api endpoints for org management.
roles
every member holds exactly one of four roles: owner, admin, developer, or member.
some actions are reserved for the owner role — transferring ownership and
deleting the organization among them. on an active paid plan, ownership
can be transferred from the dashboard.
one free-tier organization per user
you can own (hold the owner role on) at most one free-tier organization at a time. creating a new
organization is possible only while you own none.
- a paid organization never consumes the free slot — only free-tier orgs count.
- an organization pending deletion still counts against the slot until the deletion is completed.
- the default organization created at signup is exempt — it doesn’t count against the slot.
owner role and paid plans
changing who holds the owner role requires the organization to be on an active paid plan. this
covers every path to ownership:
- promoting an existing member to
owner - inviting someone as
owner - accepting an
ownerinvitation
on paid plans, all of these — including a full ownership transfer — are available from the dashboard.
deleting an organization
only the owner can request deletion, and only while no subscription is active — cancel billing
first if the org is on a paid plan.
deletion is a reviewed request, not an instant action:
- you submit the request. immediately, every api token of the organization is expired and the org is hidden from the dashboard for all members.
- crawlbrulee staff review it.
- approved — the organization and its data are permanently deleted.
- rejected — the organization becomes usable again, but its api tokens stay expired; create new tokens from the dashboard.
submitting a deletion request cannot be undone from the dashboard, and it takes every api token of
the organization out of service immediately — requests using them start failing with 401 the
moment you submit.