Manage your organization
Projects
Keep each client’s or product’s work apart inside one organization: its own systems, flows, board and environments, with the same people, roles and plan.
Open Projects in the appWhat a project is
An organization holds projects. A project is one client’s or one product’s work: its systems and APIs, flows, logic, test data, tickets, whiteboards, environments and deployments. Two projects never see each other’s systems or tickets, so a development company can keep every client apart.
Some things belong to the whole organization and are the same in every project: its members, roles and teams, the plan and billing, single sign-on, the contract policy (a project can make a check stricter or looser for itself) and chat.
A new project is open to everyone in the organization, and each person has their usual role in it. You can keep a project to the people you add, and give someone a different role in one project (see Who can see a project).
Choose a project
After you sign in, you see your organization’s projects as tiles. Click one to open it. Rabbinatix remembers the last project you opened, and opens it again next time. An organization with only one project opens it straight away.
To change project, click the name at the top of the sidebar and choose Switch project. The menu at the top of the projects page switches to another organization, or to your personal one.
Across projects
Across projects shows what waits for you in every project you can see, in one list: tickets assigned to you that aren’t done yet (Assigned to me), change sets and whiteboards you are asked to approve (Waiting for my review), and flows whose latest test run failed (Failing flows). Each row names its project. Click a row to open that project and go straight to the ticket, review or test run. Open it from the projects page, or from the menu at the top of the sidebar. The list is as it was when you opened the page: click Refresh to look again.
The chat badge on your organization, on the left of the chat page, counts what is new for you (mentions of you, direct messages and replies in your threads) in every project you can see, not only the open one.
Create a project
On the projects page, click New project. Give it a name, and optionally the client it is for and a colour. Under Start with, choose the usual setup (Development and Production, and a standard board), or the setup of another project: its environments, board columns, ticket types and tags, but none of its systems, flows or tickets. The new project reviews changes before they go live when the copied project does (or, with the usual setup, when the workspace does).
You need the Manage projects permission, which owners and admins have. How many projects you can have depends on your plan: Free has 3, Standard 25, and Premium and Enterprise have no limit. Archived projects count too.
Rename, archive or delete a project
Open the project, then go to Settings → Project.
- Change its name, client, description or colour, then click Save.
- Archive keeps everything readable, but nobody can change anything in it. Bring back makes it editable again. On the projects page, archived projects are hidden until you click Show archived projects.
- Delete removes the project and everything in it for good. To confirm, type the project’s name.
Who can see a project
Open the project, then go to Settings → Project → Who can see it:
- Everyone in the organization: every member sees the project. This is how a new project starts.
- Only people added: only the people in the list below see it. Owners, and anyone whose role has Manage projects, see every project anyway. Its tile on the projects page shows a lock and the words “Only people added”. Its chat channels are only for the people who see it.
To add someone, choose them under Choose a member… and click Add. Remove takes them off the project. Someone taken off a project they have open is sent back to the projects page. People who don’t see a project don’t find it on the projects page at all.
A role in one project
Each person in the list has a Role in this project. It starts as Organization role, the role they have in the organization. Choose any other role to use that one in this project instead, higher or lower: a Developer can be a Viewer in one client’s project, or a Viewer can be a Developer in one.
- The role in a project covers the work in it: systems, flows, logic, the board, whiteboards and chat.
- The organization’s own settings (members, roles, teams, billing, projects) always follow the organization role.
- An owner is an owner in every project.
Members and teams → Members shows each person’s roles in projects under their role, for example “Viewer in Bolt shop”.
Related
- Members and rolesInvite people to your organization, give them a role, build your own roles, group people into teams and handle access requests.
- SettingsEvery tab of Settings: your profile and the organization, single sign-on, the uptime commitment and security review, appearance, health checks, roles, tickets, chat and contract policy. Members and teams, Usage and billing, Environments and Trash have their own sidebar entries.
- Plans and billingWhat Free, Standard, Premium and Enterprise include, how to upgrade and pay through Paddle, and what happens when you cancel, a payment fails or you move down.
