Haruno Knowledge base

Members and roles

What an organization admin sees on the Organization page of a shared organization, the plan and spend tiles, the shared pool, the member table, roles and pool caps, and what an ordinary member sees instead.

  • DashboardAvailable

Once an organization has more than one member, its page is a working view of the team. Admins see everything on it. Members see less.

There are two roles. An Admin manages the organization. A Member uses it.

An admin's view of a shared organization with four members.
The Organization page for an admin of Northgate Partners. Three tiles: Plan Team, Members 4, Org spend 30d $41.37. Then Shared token pool, Members, Invitations, Your own sign-in apps and Danger zone cards.

What an admin sees

Tiles. Plan is the organization's plan, Team or Business, or "No plan". Members is the head count. Org spend (30d) is the money used in the last 30 days, in dollars. Only admins see the spend.

Shared token pool. The pool is a balance the organization holds on top of its plan. The card says how much is used, for example "$12.40 of $50.00 used", and how much is left, "$37.60 remaining". Members draw from the pool after their own seat allowance and any bonus credit. A seat is the share of the organization's plan that one member gets each cycle.

Members. One row for each member.

The member table.
The Members table. Columns: Member, Role, Tokens, Spend, Seat used, Pool cap and Actions. Four rows. One member has a seat used of 100 percent and a plus 7 dollars 45 cents line under it.
ColumnWhat it shows
MemberThe name and the email. Without a name, only the email.
RoleA drop-down: Member or Admin. Change it and it saves at once.
Tokens and SpendWhat that person used, in tokens and dollars. Together they add up to the organization's figures.
Seat usedHow much of the person's seat allowance is used this cycle. The amount under it, for example "+$7.45", is what they drew from the shared pool.
Pool capHow much of the pool the person may draw: "Uncapped" or an amount. Edit opens a box. Leave it empty for no cap. A negative number is refused.
ActionsRemove, which asks "Remove … from the organization?" first.

Seat used and Pool cap appear only when the organization has a plan. Without one, the table has five columns.

Two things are blocked: an admin cannot change their own role, and cannot remove themselves. To leave, see Leave or disband an organization.

The plan is set by our team. An admin cannot change it on this page.

The Team plan has a size limit

The Team plan holds a limited number of members, five at the moment. Inviting or accepting past it fails with "The Team plan is limited to 5 members. Upgrade the organization to Business to add more." Our team moves an organization to Business.

Below the table are the invitations, the organization's own sign-in apps and the danger zone.

What a member sees

A member sees the tiles Plan and Members, but not the spend. They do not see the pool, the member list, invitations or sign-in apps. The Members card says "Only organization admins can view and manage the member list." They can leave the organization from the danger zone.

A member's view.
The Organization page for a member. Tiles for Plan Team and Members 4. A Members card reading Only organization admins can view and manage the member list. A Danger zone card with a Leave organization button.

An organization with one member

An organization whose only member is the admin (for example just after it is made) shows only Invitations and Your own sign-in apps. The tiles, the pool, the member table and the danger zone come back once a second person joins. A pending invitation does not count.

An organization with one member.
The Organization page of an organization with only one member. The heading Northgate Partners, then only an Invitations card and a closed Your own sign-in apps card.

Last updated · PR #2944 · View this version on GitHub

History (1 version)
  1. Internal knowledge base for staff: site, reader keys, assistant, 197 pages and the PR rule (#2944)
    What changed
    @@ -0,0 +1,59 @@
    +---
    +title: Members and roles
    +summary: What an organization admin sees on the Organization page of a shared organization, the plan and spend tiles, the shared pool, the member table, roles and pool caps, and what an ordinary member sees instead.
    +feature: dashboard-organization
    +covers:
    +  - web/dashboard/app/[lang]/organization/page.tsx
    +  - web/dashboard/components/MembersTable.tsx
    +  - web/dashboard/components/StatsCards.tsx
    +  - web/dashboard/lib/format.ts
    +---
    +
    +Once an organization has more than one member, its page is a working view of the team. Admins see everything on it. Members see less.
    +
    +There are two roles. An **Admin** manages the organization. A **Member** uses it.
    +
    +<Shot src="/m/dc9e0c423cc0-dashboard-org-admin-light.webp" alt="The Organization page for an admin of Northgate Partners. Three tiles: Plan Team, Members 4, Org spend 30d $41.37. Then Shared token pool, Members, Invitations, Your own sign-in apps and Danger zone cards." caption="An admin's view of a shared organization with four members." />
    +
    +## What an admin sees
    +
    +**Tiles.** <Ui>Plan</Ui> is the organization's plan, **Team** or **Business**, or "No plan". <Ui>Members</Ui> is the head count. <Ui>Org spend (30d)</Ui> is the money used in the last 30 days, in dollars. Only admins see the spend.
    +
    +**Shared token pool.** The pool is a balance the organization holds on top of its plan. The card says how much is used, for example "$12.40 of $50.00 used", and how much is left, "$37.60 remaining". Members draw from the pool after their own seat allowance and any bonus credit. A **seat** is the share of the organization's plan that one member gets each cycle.
    +
    +**Members.** One row for each member.
    +
    +<Shot src="/m/fcf30c357ff2-dashboard-org-members-light.webp" alt="The Members table. Columns: Member, Role, Tokens, Spend, Seat used, Pool cap and Actions. Four rows. One member has a seat used of 100 percent and a plus 7 dollars 45 cents line under it." caption="The member table." />
    +
    +| Column | What it shows |
    +|---|---|
    +| <Ui>Member</Ui> | The name and the email. Without a name, only the email. |
    +| <Ui>Role</Ui> | A drop-down: **Member** or **Admin**. Change it and it saves at once. |
    +| <Ui>Tokens</Ui> and <Ui>Spend</Ui> | What that person used, in tokens and dollars. Together they add up to the organization's figures. |
    +| <Ui>Seat used</Ui> | How much of the person's seat allowance is used this cycle. The amount under it, for example "+$7.45", is what they drew from the shared pool. |
    +| <Ui>Pool cap</Ui> | How much of the pool the person may draw: "Uncapped" or an amount. **Edit** opens a box. Leave it empty for no cap. A negative number is refused. |
    +| <Ui>Actions</Ui> | **Remove**, which asks "Remove … from the organization?" first. |
    +
    +**Seat used** and **Pool cap** appear only when the organization has a plan. Without one, the table has five columns.
    +
    +Two things are blocked: an admin cannot change their own role, and cannot remove themselves. To leave, see [Leave or disband an organization](/dashboard/my-organization/leave-or-disband/).
    +
    +The plan is set by our team. An admin cannot change it on this page.
    +
    +<Callout variant="info" title="The Team plan has a size limit">
    +The Team plan holds a limited number of members, five at the moment. Inviting or accepting past it fails with "The Team plan is limited to 5 members. Upgrade the organization to Business to add more." Our team moves an organization to Business.
    +</Callout>
    +
    +Below the table are the [invitations](/dashboard/my-organization/invitations/), the [organization's own sign-in apps](/dashboard/my-organization/yayoi-app/) and the [danger zone](/dashboard/my-organization/leave-or-disband/).
    +
    +## What a member sees
    +
    +A member sees the tiles **Plan** and **Members**, but not the spend. They do not see the pool, the member list, invitations or sign-in apps. The **Members** card says "Only organization admins can view and manage the member list." They can leave the organization from the danger zone.
    +
    +<Shot src="/m/37961bcaee3a-dashboard-org-member-light.webp" alt="The Organization page for a member. Tiles for Plan Team and Members 4. A Members card reading Only organization admins can view and manage the member list. A Danger zone card with a Leave organization button." caption="A member's view." />
    +
    +## An organization with one member
    +
    +An organization whose only member is the admin (for example just after it is made) shows only **Invitations** and **Your own sign-in apps**. The tiles, the pool, the member table and the danger zone come back once a second person joins. A pending invitation does not count.
    +
    +<Shot src="/m/54bcb0ddeecc-dashboard-org-single-light.webp" alt="The Organization page of an organization with only one member. The heading Northgate Partners, then only an Invitations card and a closed Your own sign-in apps card." caption="An organization with one member." />