Nothing decides how the console divides a pool's limit between the workspaces that share the pool #336

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

The question

A pool holds an organization's limits, and every workspace of the organization draws on its default pool. A workspace is a working context inside an organization.

When two workspaces share one pool, the console has two cases:

  • Limits the console counts itself: it counts across both workspaces.
  • Limits a connected application enforces: the application enforces them per workspace. The integration contract (the messages in which the console tells an application what each holder may use) sends each workspace the number that workspace may keep in use, and a connector never adds up the workspace's siblings. So the console must divide the pool's limit between the workspaces, or refuse to let them share the pool for such a key.

How does it divide the limit?

What depends on the answer

  • What each workspace's message says when the pool allows 10 sites, one workspace holds 8 and the other holds 2, and what it says when the limit falls.
  • Whether a new workspace can get any room on a pool whose existing workspaces already hold all of it.
  • How the console decides between keeping and restricting what lies over a limit, which it decides per pool today. If a division can push one workspace below what it holds while the pool as a whole is within its limit, that decision has to move to each workspace.
  • Whether the console refuses a second workspace on a pool that carries such a key.

Options known so far

  • A common level. Every workspace may keep in use up to the same number, chosen so that what they keep together fits the pool's limit. A workspace that holds less than the level leaves its room to the others. This has been proposed but not yet examined case by case.
  • A share in proportion to what each workspace holds. Examined and rejected: it starves a new workspace, and it can make an upgrade restrict a site.
  • Refusal. Only one workspace per pool for any key an application enforces per workspace.
  • An optional part of the integration contract through which a connector declares that its application handles one amount across several of its own spaces.

Decided when

The question becomes live once it is decided whether a member may create a workspace (#139), because a pool is shared only when an organization has more than one workspace. The case can already be reached: the create-workspace route answers while its control is hidden (#241). When this closes, the resource pools model states the rule, and the integration contract's description of a workspace's message follows it.

## The question A pool holds an organization's limits, and every workspace of the organization draws on its default pool. A workspace is a working context inside an organization. When two workspaces share one pool, the console has two cases: - **Limits the console counts itself:** it counts across both workspaces. - **Limits a connected application enforces:** the application enforces them per workspace. The integration contract (the messages in which the console tells an application what each holder may use) sends each workspace the number that workspace may keep in use, and a connector never adds up the workspace's siblings. So the console must divide the pool's limit between the workspaces, or refuse to let them share the pool for such a key. How does it divide the limit? ## What depends on the answer - What each workspace's message says when the pool allows 10 sites, one workspace holds 8 and the other holds 2, and what it says when the limit falls. - Whether a new workspace can get any room on a pool whose existing workspaces already hold all of it. - How the console decides between keeping and restricting what lies over a limit, which it decides per pool today. If a division can push one workspace below what it holds while the pool as a whole is within its limit, that decision has to move to each workspace. - Whether the console refuses a second workspace on a pool that carries such a key. ## Options known so far - **A common level.** Every workspace may keep in use up to the same number, chosen so that what they keep together fits the pool's limit. A workspace that holds less than the level leaves its room to the others. This has been proposed but not yet examined case by case. - **A share in proportion to what each workspace holds.** Examined and rejected: it starves a new workspace, and it can make an upgrade restrict a site. - **Refusal.** Only one workspace per pool for any key an application enforces per workspace. - **An optional part of the integration contract** through which a connector declares that its application handles one amount across several of its own spaces. ## Decided when The question becomes live once it is decided whether a member may create a workspace (#139), because a pool is shared only when an organization has more than one workspace. The case can already be reached: the create-workspace route answers while its control is hidden (#241). When this closes, the resource pools model states the rule, and the integration contract's description of a workspace's message follows it.
cgalo5758 added the
kind
design
area/entitlementsarea/integrations
labels 2026-11-17 03:48:45 +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#336