One of the most important concepts in Policy Stack's advisor model is that seats and connections are independent. When a seat expires, the connection between you and your client does not end automatically. You retain the read/write or read-only access the client granted.
Why This Matters
This design reflects the reality of advisor-client relationships. A client relationship does not end because a billing arrangement changes. You may revoke a seat because:
- The client decided to self-subscribe to Builder Pro
- You are restructuring which clients receive seats
- The client relationship is pausing but not ending
In all of these cases, you likely still want visibility into the client's banking system data. The connection persisting means you do not need to re-invite the client or go through any reconnection process when the seat situation resolves.
What Happens When a Seat Ends
When a client's seat ends — manual revoke, downgrade-driven boot, cancellation, or freeze:
| What changes | What stays the same |
|---|---|
| The assigned seat ends; temporary Builder Pro access continues for seven days before Starter unless another source takes over | Your connection to their account |