> For the complete documentation index, see [llms.txt](https://docs.cogram.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cogram.com/projects/bulk-project-actions.md). # Bulk project actions Add members, set a stage or type, archive, or delete many projects at once from the organization project table. Select several projects in **Organization Settings > Projects > All projects** and act on all of them in one step, instead of opening each project in turn. ## Who can do this The bulk actions live only in the organization project table, which is open to **Org Admins** and **Org Owners**. The everyday **Projects** list has its own, smaller set of bulk actions. | Action | Required role | | ------------------- | -------------------------------------- | | Add members | Org Admin or Org Owner | | Set stage, Set type | Org Admin or Org Owner | | Archive, Unarchive | Org Admin, Org Owner, or Project Owner | | Delete | Org Admin, Org Owner, or Project Owner | ## Selecting projects 1. Go to [Organization Settings > Projects](https://app.cogram.com/dashboard/settings/admin/projects). 2. Narrow the list first with search, **Filters**, or **Source**. Filtering by member, client, type, or stage is usually faster than hunting through pages. 3. Tick the checkbox on each project, or the checkbox in the header to select every project **on the current page**. The action buttons appear above the table once at least one project is selected. > **Selection covers one page at a time.** The header checkbox selects the page you are looking at, not every project matching your filters. To act on more projects at once, raise **Rows per page** at the bottom of the table before selecting. ## Adding members to several projects **Outcome**: the people you pick hold the role you choose on every project you selected. 1. Select the projects. 2. Click **Add members**. 3. Search for people on the left and click to add them. Only existing members of your organization appear here — invite new people in **Organization Settings > Users** first. 4. Set each person's role on the right: **Owner**, **Member**, or **Viewer** (plus **Lead**, if your organization has that role turned on). The role applies to every selected project. 5. Check the project list under **N projects selected**. Click **Remove** on any project you did not mean to include. 6. Choose what happens to anyone who already has a role on one of these projects: * **Leave them as they are** — their existing role is untouched. * **Change their role to the one set above** — their role is replaced. 7. Tick **Email everyone about their new projects** if you want people notified. This sends one email per person per project, so a large selection sends a lot of mail. It is off by default. 8. Click **Add N people to N projects**. **Expected result**: a confirmation appears, and the **Members** column updates on the projects you selected. Adding someone as **Owner** does not replace the project's existing owner. A project can have several owners. > **Owner cannot be granted through a group.** If you need people to own projects, add them here or in project settings. Groups can grant Lead, Member, or Viewer only — see [Project roles](/projects/project-roles.md). ## Setting a stage or type 1. Select the projects. 2. Click **Set stage** or **Set type**. 3. Pick a value from the list, or choose **Clear stage** / **Clear type** to empty that column. **Expected result**: the **Stage** or **Type** column updates on every selected project. Stages and types have to exist before you can assign them. Create them in [Project stages](https://app.cogram.com/dashboard/settings/admin/projects) and [Project types](/projects/project-types.md). ## Archiving and deleting **Archive** hides projects from the active list while keeping their content. Select archived projects and click **Unarchive** to bring them back. **Delete** removes the projects and their content permanently. You are asked to confirm, and the action cannot be undone. ## Troubleshooting **Symptom**: after adding members, a panel says **Partly applied** or **Nothing was changed**. **Likely cause**: some project-and-person pairs could not be changed. The panel groups them by reason. **Fix**: read the reason next to each pair. | Reason | What it means | | ---------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | | Already had a role on the project | The person is already a member. Re-run with **Change their role to the one set above** if you meant to change it. | | Already had exactly this role | Nothing to do. | | You can't add members to these projects | Personal workspaces, which never take members. | | Project no longer exists | The project was deleted while the dialog was open. | | No active account for this email | The account was removed or suspended. | | That role is not enabled for your organization | The **Lead** role is not turned on. Pick another role. | *** **Symptom**: someone shows in the **Members** column but adding them again still changes something. **Likely cause**: they had access through a [group](/organization-administration/groups.md), not directly. Group access does not give them a role of their own. **Fix**: this is expected. Adding them directly gives them their own role, which is the only way to make a group member an **Owner**. *** **Symptom**: the request is refused, saying too many memberships would change at once. **Likely cause**: projects multiplied by people is over the limit for one request. **Fix**: select fewer projects or fewer people and repeat. You can add at most 50 people to at most 500 projects in one step, and no more than 10,000 project memberships in total. ## Next steps * [Project roles](/projects/project-roles.md) — what Owner, Lead, Member, and Viewer can do * [Groups](/organization-administration/groups.md) — grant recurring access to many projects without repeating this * [Project templates](/projects/project-templates.md) — pre-bind groups and roles on new projects * [Project import](/projects/project-import.md) — set owners and members while importing projects from a spreadsheet --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.cogram.com/projects/bulk-project-actions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.