Every person in a team has a role. The role defines what they can see and do. That keeps it clear who creates posts, who approves them and who manages the team.
Who can do what – the full overview
This table shows you exactly which role has which permissions. It matches the overview in your team under Members one to one and is always up to date.
| Right | Junior | Member | Admin | Owner | Approver internal | Approver external |
|---|---|---|---|---|---|---|
| View + comment on posts | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Approve + reject posts | – | ✓ | ✓ | ✓ | ✓ | ✓ |
| Create, edit + delete drafts | ✓ | ✓ | ✓ | ✓ | – | – |
| Upload + manage media (on own posts) | ✓ | ✓ | ✓ | ✓ | – | – |
| Edit + delete posts after approval | – | ✓ | ✓ | ✓ | – | – |
| Edit content of assigned approval posts | – | ✓ | ✓ | ✓ | ✓ | – |
| Create approval links (post + pools) | – | ✓ | ✓ | ✓ | – | – |
| View custom PIN | – | ✓ | ✓ | ✓ | – | – |
| View approver PINs | – | – | ✓ | ✓ | – | – |
| Set approval/publishing status | – | ✓ | ✓ | ✓ | – | – |
| View analytics (Insights + Prime Time) | – | ✓ | ✓ | ✓ | – | – |
| Create + edit projects | – | – | ✓ | ✓ | – | – |
| Invite + remove members | – | – | ✓ | ✓ | – | – |
| External approvers + team settings | – | – | ✓ | ✓ | – | – |
| Adjust standard approval flow | – | – | ✓ | ✓ | – | – |
| Delete projects / team + plan | – | – | – | ✓ | – | – |
✓ = allowed, – = not allowed. „Approver (internal)" is a person with a login just for approving; „Approver (external)" approves via a link with PIN, without an account.
What sets the roles apart
Junior
A Junior can view posts, comment and create and edit new drafts. But as soon as a post goes into approval or is published, a Junior can no longer change it. Sending posts for client approval and publishing aren't possible for Juniors either. So it's ideal for doing the groundwork in peace, without anything going out by accident.
Member
A Member covers the entire content workflow: creating posts, editing them, sharing them for approval, setting the approval status and publishing. What a Member can't do are structural team changes such as creating projects or inviting members.
Admin
An Admin can do everything a Member can, and on top of that manages the team: creating and renaming projects, inviting members and removing them, as well as maintaining external approval people. Inviting other admins or changing roles, however, is something only the owner can do.
Owner
The Owner is the team's owner. They have all permissions: changing roles, renaming and styling the team, managing the plan, and even deleting the team again. Each team has exactly one owner.
Note: Higher roles can do everything the lower ones can – and more on top.
The internal approver – a special role
Alongside the four levels there's also the internal approver. This role sits a little sideways to the order: such a person can view, comment on, approve or reject posts – but can't create, publish or manage anything themselves. There's exactly one editing exception: on posts assigned to them for approval, they can make the adjustments that were enabled when sharing – changing the caption or date, cropping, or uploading their own media, each only if the corresponding option is switched on for that post. It's meant for stakeholders with their own login, for instance from management or the legal side, who should give their okay directly in maebe.
The role isn't a requirement for approving, though: as a post's approver you can name any team member except juniors – members, admins or the owner too. More under Internal approval.
External approval people
Should someone only approve, but have no login at all – for example your client? That's what external approval people are for. They aren't team members and confirm posts conveniently with a name and a PIN.