What group Admins, Leads, and Members can do: the board, posts, inviting and removing members, reports, group settings, and who can delete the group.
Group member roles control what a user can do within a specific group. Each group member is assigned one of three roles: Admin, Lead, or Member. The group creator automatically becomes the group Admin.
The table below shows what each group role can do.
| Capability | Admin | Lead | Member |
|---|---|---|---|
| View group content | ✓ | ✓ | ✓ |
| Post & use Arkboard | ✓ | ✓ | ✓ |
| Delete Arkboard columns | ✓ | ✓ | — |
| Permanently delete ark cards *** | ✓ | — | — |
| See group Reports **** | ✓ | ✓ | — |
| Delete others' posts | ✓ | ✓ | — |
| Pin/unpin posts | ✓ | ✓ | — |
| Invite members | ✓ | ✓ | — |
| Approve join requests | ✓ | ✓ | — |
| Remove members | ✓ | ✓ | — |
| Pin/unpin group | ✓ | ✓ | ✓ |
| Change member roles | ✓ | — | — |
| Edit group settings (name, description, intro) | ✓ | — | — |
| Delete group * | ✓ | — | — |
| Review ark highlight registrations ** | ✓ | — | — |
* For org-owned external groups, only Admins from the owning organization can delete it. For individual-created groups, only the creator can delete the group.
** Group Admins can approve or decline registrations for ark highlights that feature cards from their group. Organization Admins can also review all registrations across the organization.
*** Anyone who can edit the Arkboard can delete ark cards nobody else is on (soft-delete to the 30-day Recently deleted window); cards people are on take an Admin, a Lead or the card's Responsible person. Permanently erasing a card requires the card's creator (while they can edit the Arkboard) or a Group Admin, so one teammate can't wipe another's work beyond recovery. See Arkboard System.
**** This is the default. Group Admins can open Reports to every member, or hide the tab entirely, from Reports access in Group settings. See Group Reports.
There are three ways someone becomes a member of a group, with different lifecycles and admin tools.
Both can lead to membership but they're initiated differently:
| Action | Cooldown for the user | What admins see |
|---|---|---|
| Admin declines a join request | 3 days before they can request again | No re-surface — the request is removed from the pending list |
| User declines an invitation | None — they can join (Open groups) or request again immediately | An "Invitation updates" entry surfaces in the pending-requests panel for 3 days, then auto-clears. Admins can dismiss the section at any time. |
When someone accepts an invitation, the Admin or Lead who sent it gets a notification. Acceptances in the same group add to that one notification until they read it. Nobody is notified when an invitation is declined: it shows in the "Invitation updates" section under Member Requests on the group's Members tab.
Groups have three privacy configurations that determine who can discover and access them.
| Type | Who can discover | Who can view content | Who can participate |
|---|---|---|---|
| Open | Everyone | Everyone | Members only |
| Private | Everyone (preview page) | Members only | Members only |
| Hidden | Members only | Members only | Members only |
Note: Organization Admins can always discover and view all internal groups (including hidden) within their organization, and can edit group settings and delete them. For external groups, this override only applies to groups owned by their organization. Member management (invite, remove, change roles) and participation (posting, arkboard) require joining the group.
Cross-org capability: Organization Admins can also withdraw their own organization's members from external groups owned by other organizations. This pulls every org-mate out of that group at once and is intended for situations where the org no longer wants its team participating (e.g., ending a vendor engagement). Available from the group header menu on any external group not owned by the admin's org.
If you're part of an organization, your org role also affects what you can do. See Organization Member Roles →