Invite your team
Flags are better with company. In a couple of minutes you’ll have a teammate in your organization with exactly the role and project access you meant them to have.
You’ll need to be an Admin or Owner to invite people.
1. Create the invitation
Section titled “1. Create the invitation”Open Admin → Users and create an invitation. You’ll choose, right on the invitation:
- A role — Viewer, Developer, Admin, or Owner. (You can’t grant a role above your own.) Not sure? Start with Developer for someone who’ll work with flags, Viewer for someone who just needs to see them — the full matrix is one page.
- Project access — for Viewers and Developers, tick the projects they should see. Projects you don’t grant are invisible to them, so a contractor scoped to one project genuinely sees one project.
2. Share the link — you deliver it, not us
Section titled “2. Share the link — you deliver it, not us”Creating the invitation gives you an invite link, shown to you in the dashboard. FortressFlag doesn’t send email — so copy the link and share it with your teammate yourself, over whatever channel you already trust: your team chat, a direct message, however you’d share anything else meant for exactly one person.
Treat the link with a little care — it carries the invitation, so it’s for your teammate, not for a public channel.
3. They accept
Section titled “3. They accept”Your teammate opens the link, sets up their account (name, password), and accepts the service terms as part of joining. That’s it — they land in the dashboard with the role and project access you chose, and the audit log records the whole thing.
If they already use FortressFlag with another organization, accepting simply adds yours to their account — one person, one login, many organizations.
Adjusting later
Section titled “Adjusting later”Roles and project grants aren’t set in stone: Admins change both any time from Admin → Users, and every change lands in the audit log.
Where to next
Section titled “Where to next”- Roles and safety — what each role can actually do
- Require approval for production changes — now that there are two of you
- Require two-factor authentication — before the team grows further