Who may open a product

Context and Problem Statement

Teams were drawn as groups of members that a product is shared with. That was a second list of people to keep, to answer one question: who can open this product. Revised by the owner on 2026-10-18: there are no teams.

Considered Options

• Teams: groups of members, and a product shared with teams is open only to them.
• Each product says who can open it: everyone in the company, or chosen people.

Decision Outcome

Each product says who can open it, chosen by the owner on 2026-10-18.

• Everyone in the company is the default.
• Chosen people: only the members picked for that product.
• The owner can always open every product.
• Only the owner changes who can open a product, on settings.
• A person's access level (Owner, Can merge, Can edit, Can view) is unchanged by this. It is per person and company-wide, and says what they may do in a product they can open. See access-levels.

Consequences

• The rule is kept in the database, as row-level security on the product and on every table that belongs to a product. The web app says who is asking with withMember; a query cannot forget the rule. See tenant-isolation.
• The capture worker has no person and sees every product of the company it is working for.
• Removing a member removes them from every product's chosen people.
• A preview link is read by its secret before any company is known, so reading one is not narrowed by this rule. Making one is.