Company settings
Company settings holds the five things about your company that are neither a person nor an invoice: its name, its billing contact, its default team, its seat policy and its position on join codes.
What it does
Company name is what appears at the top of the console and in invitations.
Billing contact email is where billing notices are addressed. Stripe still emails whoever owns the payment method, so this does not replace that.
Default team is where a new person lands when their invitation names no team. Every company has one — it was created for you, called General, when your company was set up. The default team cannot be archived, so if you want to retire it, point this setting at another team first.
Seat policy decides when an invitation costs you a seat:
- Seats are consumed when an invitation is accepted — the default. A pending invitation reserves nothing. Invite freely, pay for people who join.
- Seats are reserved when an invitation is sent — stricter headcount control. A pending invitation holds a seat until it is accepted, revoked or expires, and sending one is refused when the pool is full.
Join codes is a checkbox recording whether your company accepts shared join codes alongside per-person invitations. It is a policy record: clearing it does not switch off a code that has already been issued. A join code lasts seven days, there is only ever one live code per company, and generating a new one replaces the old one. To stop a code working sooner, generate a new one, or ask Roadmap Flow support to clear it.
Company identifiers shows your organization ID and creation date. Quote the organization ID when you contact support.
When to use it
- Your company was named from a Stripe checkout field and reads oddly.
- Finance changed and billing notices should go elsewhere.
- New people are landing in the wrong team by default.
- You want to stop paying for invitations that are never accepted — or the opposite, to hold seats the moment you invite.
- You have moved off join codes and want that written down.
When not to use it
- To cancel or change the subscription. That is Seats and billing and the Stripe portal.
- To change one person's seat. That is People.
- To rename a team. That is Teams.
3-minute flow
- Open Company settings.
- Correct the company name if it reads like a checkout field.
- Set the billing contact.
- Point the default team at the group most new people belong to.
- Choose a seat policy — leave it on the default unless headcount control matters more than convenience.
- Click Save settings.
Best use cases
- A first-week tidy after buying Team, so the console reads like your company rather than a receipt.
- Switching to the strict seat policy in a company where budget is approved per head and an invitation is effectively a commitment.
- Moving the default team from General to the squad that actually onboards people.
Common mistakes
- Expecting the join-code checkbox to revoke an existing code. It does not; generate a new code or wait out the seven days.
- Switching to the strict seat policy while your pool is full, then wondering why invitations are refused. They are refused because there is no seat to reserve.
- Changing the company name and expecting the Stripe invoice to change. The invoice name comes from Stripe.
Related guide pages
Availability
Team. Reachable by the company owner and company administrators. Every change made here is written to the audit log.