Status. Proposed design only. Nothing in this vault is GGA client approval. The GGA client documents are supplied drafts: see GGA-Source-Digest. No application, service or test has been executed; every scenario is Not executed. Delivery fees and dates are open.

GQ03 · Multiple memberships and the company role set

FieldValue
StatusOpen question (raised while reconciling the GGA documents with vault 1.3)
AuthorityClient (GGA). The repository owner may route and record it but cannot decide client policy
Needed beforeIdentity design, Q01, Q02, Q19
Answer / approver / date[ ]

Question

May one user belong to several companies (the data model allows invited colleagues; the default is one selected company context per session)? Do the finer 1.3 company roles (approver, contributor, viewer), assignment and company-admin disclosure survive inside a company?

Handling until answered

Both readings stay visible in the vault; no scenario oracle depends on a guess. An owner answer without the client authority is recorded as “owner recommendation; client decision pending”. Index: Decision-Index.