Plan is the fifth section along the top of Settings, before Developer, and it holds two groups: Subscription and Invitations.
If your account is a member seat on someone else's team, there is no Plan section at all — the seat is the company's and every billing control belongs to the person who owns it. You get a Team section in its place.
If you came looking for invites and expected a section of their own, this is the screen. They are a group here rather than a top-level pill.
Subscription
The card reports the state your account is in, and the states are not synonyms:
- Trial — you are inside the trial window. The date to watch is Trial ends.
- Active — a running subscription, billed Monthly or Annual. The date is Current period ends, which is when it renews rather than when it stops.
- Past due — a payment did not go through. Grace period ends is the date that matters, and it is the one worth acting on, because it is a deadline rather than a renewal.
- Canceled — cancellation is recorded and the account still works to the end of what you paid for. It carries both Current period ends and Cancels on.
- Locked — access is restricted.
Read the state and its date together. "Current period ends" on an active subscription and "Grace period ends" on a past-due one look alike on screen and mean opposite things: one is business as usual, the other is a countdown.
Changing a card, a plan, or cancelling happens in the subscription portal, which this screen opens for you. Billing itself is handled outside Brief, so that is where the payment details live.
Not every account gets that button, and the card says why. If your team pays for Brief, the card names the team and the colleague who holds your seat, and points you at See your team — every billing control belongs to them, not to you. If Brief invoices your team, or provides it at no charge, the card tells you to ask your Brief contact instead: there is nothing self-serve to open.
Invitations
Brief accounts are invitation-only, and this is where you spend yours.
Type a colleague's work address in the field — colleague@example.com, say — and send. Each account has a quota, so the count is finite.
Sent invites are listed with their state. Pending means it has gone out and has not been accepted; before you have sent any, the list reads "No invites sent yet." An invite you no longer want honoured can be revoked from its row.
An invited colleague signs in exactly as you did, through Google or Microsoft, and gets their own private account. Their data stays isolated from yours. What changes is that briefings for meetings you both attend can reflect shared context, built only from what each of you can already see in your own systems.
Two practical notes. Invite the work address the person actually reads, because that is the account they will connect and the one Brief will sync. And if an invite was never received, have them check spam before you revoke and resend — a revoked invite is spent from the quota either way.
For the sign-in flow your colleague will meet, and the admin-approval errors that can block it, see Getting started with Brief, If Google blocks your sign-in, and If Microsoft blocks your sign-in.