Activity permissions on the project
Not every project member needs to see and edit every activity. On a large team, a board full of other people’s cards becomes noise; on an open team, locking everything to the manager stalls the day.
In Rabbiit this is configured per project, on the Activities tab of project edit. The default comes from general account settings: a new project inherits that set. Then the manager (or the administrator) adjusts only the project that needs a different rule.
The administrator and the project manager always do everything on that project’s activities. The rules below apply to members.
💡 Plan: the account default for activities on new projects is part of the global project settings (paid plans with this feature). Without the feature, the previous behavior remains: the member sees and edits the entire board.
What you can control
Project modal, activity permissions tab
There are two blocks, the same on the account and on the project.
Visibility
- All project activities — the member sees the entire board, including other people’s cards.
- Only activities assigned to the member — the member sees only those where they are the assignee (and the subactivities of those cards).
Actions — for each one, choose who can: Project manager, All members, or, on several of them, Assigned member.
- Create — open a new card
- Edit — title, description, and subactivities
- Complete
- Comment
- Change assignee
- Modify planning — hour estimate, due date, and the other planning fields
- Move / reorder
- Delete / restore
- Manage lists — create, rename, reorder, and delete the lists (columns) on the board
Create, change assignee, move, and manage lists do not have the “assigned member” option: it is either the manager, or all members. It would not make sense for “only the assignee to create the card that does not exist yet”.
Account default (inheritance)
- Open account settings.
- In the Default activity settings for projects section, set visibility and actions.
- Save. That set becomes the default for new projects.
Projects that already exist do not change on their own when you change the account default. Inheritance happens at creation. If an old project needs the new rule, open its edit screen and adjust the Activities tab.
This is the same spirit as the privacy or capacity default: the account sets the starting point; the project can differ.
Adjustment on each project
- Open the project and Edit project.
- Go to the Activities tab.
- Review or change what the member can see and do on this project.
- Save.
Only someone who can edit the project changes these rules (administrator or super user with permission to manage that project).
Use the project for the exception: a confidential client with visibility only for the assignee; an internal squad where everyone creates and comments.
How to combine it with day-to-day work
Small team, high trust — let the member see all activities and create/comment. The board is the team conversation.
Several clients on the same project — restrict visibility to assigned activities. The member does not see the other client’s card.
Estimate and due date in the manager’s hands — Modify planning only for the manager. The member executes and comments; they do not change the agreed size. Sum details are in hour estimates.
Attachment and conversation on the card — without Comment permission, the member does not discuss on the card. See attachments and comments.
These rules belong to the project, not the account profile. The user profile (standard, super user, administrator) defines the rest of the account. Here what applies is the slice of that project.