Organization Management

Organizations are the top-level ownership unit in Jinba Toolbox. Every ToolSet, API key, and execution record belongs to an organization. You must belong to an organization before you can start building tools.

Opening an Organization

Organizations, memberships, roles and invitations are managed in JinbaAuth, the shared Jinba sign-in service — the Toolbox console cannot create organizations or invite members.

Open the Dashboard

After signing in, the dashboard shows Your Organizations — the organizations you belong to, each with your role and its ToolSet count. If the list is empty, organizations will appear here once you are invited to one in JinbaAuth.

Open an Organization

Click an organization card. You land on its Tool Sets page, ready to start building. The organization switcher in the top bar lets you jump between organizations.

Organization Dashboard

Once inside an organization, the sidebar provides access to all management areas:

Tool Sets

View, create, and manage your ToolSets. This is the default landing page for an organization.

Runs

Browse the execution history of all tools within the organization.

API Keys

Create and delete API keys scoped to this organization.

Webhooks

Members

See who belongs to the organization and their roles.

Settings

View the organization’s name, slug, logo and SSO login URL.

The credit balance is shown at the bottom of the sidebar; clicking it opens the Credits page where you can purchase credits and review transaction history.

Member Management

The Members page in the organization sidebar is read-only. It lists each member with their role and join date, and shows pending invitations (email, role, invited by, expiry) when there are any. Inviting members, changing roles and removing members are done in JinbaAuth, not in the Toolbox console.

Invitation Links

An invitation link opens the /invite/[id] page in the Toolbox console. The page shows the organization, the invited role and e-mail, and whether the invitation is expired, already accepted or cancelled, then points you to Open JinbaAuth to review and accept the invitation there. If you are signed in with a different e-mail address than the one invited, a warning is shown.

Roles and Permissions

Each member has one of the roles Owner, Admin or Member (assigned in JinbaAuth). Inside Jinba Toolbox the roles grant:

Permission	Owner	Admin	Member
Create / edit / delete / publish ToolSets and Tools	Yes	Yes	Yes
Execute and test tools	Yes	Yes	Yes
View run history and members	Yes	Yes	Yes
Create API keys, delete own API keys	Yes	Yes	Yes
Delete other members’ API keys	Yes	Yes	No
Create, edit and delete webhooks	Yes	Yes	No
Purchase credits	Yes	Yes	No

API keys always act with Member-level permissions, regardless of who created them.

Organization Settings

Settings in the sidebar shows the organization details: logo, Organization Name, Organization Slug and, for organizations with SSO configured, the SSO Login URL (/login?tenant={slug}) with copy and open buttons. These fields are read-only in the Toolbox console; organization details are edited in JinbaAuth.

Best Practices

Use organizations to group related teams or projects. Each organization has its own ToolSets, API keys, and credits.
Follow the principle of least privilege. Assign the minimum role needed for each member (in JinbaAuth).
Review members regularly. Remove access for users who no longer need it.
Keep at least two Owners for redundancy in case one becomes unavailable.

​Opening an Organization

​Organization Dashboard