An organization of several people cannot give each of its members an amount of a resource #335

Open
opened 2026-11-17 03:48:32 +00:00 by cgalo5758 · 0 comments
Owner

The question

An organization's limits sit on its pools. They reach a connected application through the integration contract: the messages in which the console tells an application what each holder may use. A holder is either a workspace (a working context inside an organization) or a person.

  • A workspace's number covers things the workspace holds, such as a team folder or a mail domain.
  • A person's own space, such as a home folder, the repositories a person owns or a person's rooms, gets its number only from the person's personal organization: the one the console creates at the person's first sign-in.

Nothing lets an organization of several people give each member an amount. Neither "20 GB of home for each member" nor "500 GB for the team, split as the administrators choose" is possible. Should the console offer this, and how?

What depends on the answer

  • Whether a cooperative can sell a team plan that sizes each member's space. Making resources allocatable is what the console is for, and selling is one way to allocate.
  • Who an organization's people are when an amount is counted per member, and what leaving means for what a member stored under the team's amount.
  • Whether an amount per member grows the organization's total when someone joins. That needs quantities above one, which the console does not sell today, and it touches whether buying two of something gives twice the allowance (#83).
  • What the integration contract carries. Today a workspace's message names no person, and the application divides the workspace's number with its own controls, for example the mailbox sizes a mail domain's administrators set.

Options known so far

  • A share of a workspace's limit, given to each listed person, and delivered only where the application keeps a per-person amount inside the team's thing (a mailbox inside a domain). Examined and set aside for now: it fixes a shape for the list of an organization's people, and puts each person's holdings into stored reports, before any organization of several people exists.
  • An amount per member set by the plan ("20 GB each"), growing the total as members join. This needs seats.
  • A team's share added to a person's own number, or the larger of the two: rejected. Another organization could add a person for one day and restart the countdown toward losing what is over their limit. Ending its share could also start the removal of the person's own files.
  • A workspace for each member with its own pool: rejected. Two numbers still meet in one home folder, and a mailbox in the team's domain has no place.

Decided when

This waits on invitations (#75), because until a member can bring another person in, no organization has several people. If invitations are scheduled before the public launch, this is decided with them, since the first version of the integration contract is fixed at launch. When it closes, the identity and entitlement models state:

  • who an organization's people are;
  • whether and how an organization gives each of them an amount;
  • what happens to that amount when a person leaves;
  • the optional part of the integration contract a connector declares to receive it.
## The question An organization's limits sit on its pools. They reach a connected application through the integration contract: the messages in which the console tells an application what each holder may use. A holder is either a workspace (a working context inside an organization) or a person. - A workspace's number covers things the workspace holds, such as a team folder or a mail domain. - A person's own space, such as a home folder, the repositories a person owns or a person's rooms, gets its number only from the person's personal organization: the one the console creates at the person's first sign-in. Nothing lets an organization of several people give each member an amount. Neither "20 GB of home for each member" nor "500 GB for the team, split as the administrators choose" is possible. Should the console offer this, and how? ## What depends on the answer - Whether a cooperative can sell a team plan that sizes each member's space. Making resources allocatable is what the console is for, and selling is one way to allocate. - Who an organization's people are when an amount is counted per member, and what leaving means for what a member stored under the team's amount. - Whether an amount per member grows the organization's total when someone joins. That needs quantities above one, which the console does not sell today, and it touches whether buying two of something gives twice the allowance (#83). - What the integration contract carries. Today a workspace's message names no person, and the application divides the workspace's number with its own controls, for example the mailbox sizes a mail domain's administrators set. ## Options known so far - A share of a workspace's limit, given to each listed person, and delivered only where the application keeps a per-person amount inside the team's thing (a mailbox inside a domain). Examined and set aside for now: it fixes a shape for the list of an organization's people, and puts each person's holdings into stored reports, before any organization of several people exists. - An amount per member set by the plan ("20 GB each"), growing the total as members join. This needs seats. - A team's share added to a person's own number, or the larger of the two: rejected. Another organization could add a person for one day and restart the countdown toward losing what is over their limit. Ending its share could also start the removal of the person's own files. - A workspace for each member with its own pool: rejected. Two numbers still meet in one home folder, and a mailbox in the team's domain has no place. ## Decided when This waits on invitations (#75), because until a member can bring another person in, no organization has several people. If invitations are scheduled before the public launch, this is decided with them, since the first version of the integration contract is fixed at launch. When it closes, the identity and entitlement models state: - who an organization's people are; - whether and how an organization gives each of them an amount; - what happens to that amount when a person leaves; - the optional part of the integration contract a connector declares to receive it.
cgalo5758 added the
kind
design
area/identityarea/entitlementsarea/integrations
labels 2026-11-17 03:48:32 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: wiki-cafe/member-console#335