Organizations
Group projects and members into organizations, invite teammates, and set a wildcard domain.
An organization is the top-level workspace that owns your projects, servers, and members. You can belong to several organizations and switch between them, which is useful for separating clients, teams, or business units.
Creating an organization
Provide a Name and, optionally, a Logo, then mark one organization as your default so it is selected automatically when you sign in.
On a self-hosted instance, only the Owner of your current organization can create additional organizations. On Skitflow Cloud any member can create one, up to the number of organizations allowed by the billing plan.
Deleting an organization
Only the organization's owner can delete it, and you must always remain the owner of at least one organization — deletion is blocked if this would be your last one.
Inviting members
Invite teammates by email and assign them a role:
- Admin — full management of the organization's projects and settings.
- Member — scoped access; combine with Permissions and Custom Roles for fine-grained control.
Pending invitations can be resent or removed. Invited users join the organization once they accept.
Wildcard domain
Each organization can define a wildcard domain (for example *.apps.example.com). Skitflow then uses it to auto-generate domains for new services, so every application gets a unique hostname without manual DNS work. See Domains for how generated domains are assigned.
Point a wildcard DNS record (*.apps.example.com) at your server before enabling the wildcard domain, so generated hostnames resolve immediately.
Code Review governance
Organization owners and admins can manage Code Review feature availability, automatic-review limits, token and cost budgets, and the behavior used when a budget is exhausted under Dashboard → Settings → Code Review. Organization limits apply across repositories; repository settings can narrow supported budgets further.
Budget limits affect review behavior, not only reporting. At 80% usage, reviews use diff-only context. At 100%, automatic reviews are skipped; interactive reviews degrade to diff-only by default or can be blocked explicitly. See Code Review scaling and limits for the complete self-hosted operator contract.