PlanewardPlaneward Docs
PlanewardPlaneward Docs
Welcome
Account settingsWorkspace settingsPayment processorsRoles and permissions

Developers

REST APIAuthenticationWebhooksMCPEmbedded projectsTask description contentDeveloper hub

API

Settings

Roles and permissions

Create roles, turn permissions on, and assign them to people.

Who can do what is layered. A person is an Owner or a Member. Members get one or more roles. Roles decide what they can do across the workspace. A project or a chat channel can still tighten or widen that.

Open Settings

Open Settings in the sidebar, then Roles to create and edit roles. Open Members to invite people and change who has which role. ⌘K can jump to either tab.

You need Manage roles to create and edit roles. You need Manage members to assign roles, suspend, or remove people. The owner can do all of this.

Owner and Member

  • Owner — the person who created the workspace, or received it via transfer. They skip roles. They can do everything.
  • Member — a full teammate. They hold workspace roles.

Project access is for workspace members. To give someone outside the team a project, invite them to the workspace first. Clients see their invoices in the client portal.

Built-in roles

Every workspace starts with two protected roles. You cannot rename or delete them.

  • Admin — every workspace permission. Treat this like a workspace operator.
  • Member — the default for new invites. They can view the workspace, members, and activity; create projects; view customers, contacts, and pipelines; and view chats. They cannot see money (invoices, payments), cannot open every project, and cannot manage members or roles.

You can still change the switches on these roles.

Create a role

  1. Open Settings, then Roles.
  2. Click New role.
  3. Give it a Name (for example Finance) and a color.
  4. Click Create role.

The new role starts with no permissions. Select it in the list.

Turn permissions on

Open the Permissions tab. Products match the sidebar: CRM, Chats, Email Sending, Community, Commerce, Integrations, Sites, Developer, Projects, and Workspace. Turn a product on for this role, then tick View or Manage. It saves immediately.

You can only turn on a permission you already have. You cannot edit or assign a role at or above your own rank. Drag roles in the list, then Save order — higher in the list is a higher rank.

Manage roles is marked dangerous. Someone with it can create roles and assign anything below their rank.

If Apps turned an app off for the workspace, that block is greyed out until you turn the app back on.

What the groups cover

CRM — Customers, contacts, forms, pipelines, invoices, and payments. Each row is View or Manage. View forms opens a form's submissions and Analytics; Manage forms also turns on, regenerates and turns off its public results link. The default Member role has no money rows.

Chats — View channels, create and configure them, or delete other people’s messages.

Community — View, Manage or Moderate the community: its settings (General, Branding, Theme, Domain, Sign-in and Emails tabs), memberships and channels.

Commerce — View commerce shows the catalog, receipts, checkout links, revenue share and balances. Manage commerce changes products, plans, what buyers get, promo codes, affiliates and receipt review, and can cancel a member's subscription. Every Commerce page needs View commerce or Manage commerce; View payments or Manage payments alone opens none of them. Reviewing withdrawals needs Manage payments plus a Commerce permission, and so does changing payout details (Manage payments or Manage commerce). Changing which products sell an event or unlock a course needs Manage commerce. Turning a product's community access on needs Manage commerce and Manage community. Changing sign-in methods needs the manage permission of every app that is on. See Commerce.

Developer — API keys, webhooks, and workflows.

Projects — create projects, or Manage any project to open and administer every project without a grant.

Workspace — view the workspace, change its settings, read the activity log, and manage members or roles.

A person with more than one role gets the union of those checkboxes.

Give a role to people

Two places do the same job.

From Members

  1. Open Members.
  2. Find the person. The Roles column shows what they have.
  3. Click it, check or uncheck roles, and apply.

The row menu can Suspend or Remove a member. Suspended people cannot use the workspace until you restore them. You cannot do this to the owner.

From the role

  1. Select the role.
  2. Open Members.
  3. Click Add Member, search by name or email, and pick them.

You can also grant the role when you invite. Leave the role picker empty to give them the default Member role.

Project access on top

Workspace roles do not open every regular project. The owner can. Anyone with Manage any project can. Everyone else needs a grant.

On a project, Settings → Project access, then Grant access:

  • Workspace role — everyone with that role gets Viewer, Editor, or Project manager.
  • Member — the same levels for one person.

You can also grant from the role’s Projects tab.

Pipelines live under CRM, not as a special project. Grant View pipelines / Manage pipelines on the role. Anyone with those permissions can work the boards. You do not grant a pipeline like a regular project.

See project settings for what Viewer, Editor, and Project manager can do.

Roles can also be assignees on tasks. A role can be assigned in a project when it has Manage any project, or Editor or Project manager access to that project. Everyone who holds the role then owns the task. See assigning roles.

Chat channels on top

View chats gets someone into Chats. Manage chats lets them create channels. Moderate chats lets them delete messages they can see.

Channel settings can still Allow, Deny, or Inherit things like sending messages, attaching files, starting threads, and managing the channel. Inherit uses the workspace defaults. See Chats.

Role settings

On General, change the name, description, and color. Admin and Member keep their names; you can still edit description and color.

On Settings:

  • Display separately — show people with this role in their own section, in Communications and in the community members list. In community chats, the role also shows beside their name. With it off, they're listed with everyone else and get no badge.
  • Mentionable — allow @role mentions in chats.

Delete only works after you remove the role from every member. Protected roles cannot be deleted.

View as a teammate

Check what someone on your team can actually see. View as shows you the whole workspace through their eyes: the sidebar, ⌘K, pages, buttons, data, projects, chat channels and live updates all follow their roles, their project access and the channels they belong to.

Who can use it

  • The owner can view as any member.
  • A member whose roles grant every workspace permission (like Admin) can view as teammates ranked below them.
  • Nobody can view as the owner, and you can't view as yourself.

Start and exit

  1. Open Settings, then Members.
  2. Open the row menu on a teammate and choose View as.

A banner at the top reads Viewing as {name} · {role} · Read-only. Click Exit in the banner to go back to your own view. View as also ends on its own after 1 hour, and it only applies to this workspace. Your other workspaces look the same as always.

It's read-only

You can look, but not change anything. Anything that would save, send or delete is blocked with "You're viewing as {name}. Exit view as to make changes."

Reading still works: open pages, scroll chat history, search and filter.

Good to know

  • They don't appear online. Your visit doesn't show them as online in chats, and you don't show up either.
  • Your bell and account menu stay yours. Notifications and your account settings are still your own, not theirs.
  • It's recorded. Starting view as adds a Viewed as teammate entry to the workspace Activity log.

Next

  • Workspace settings
  • Getting started
  • Project settings

Payment processors

Connect Stripe, Xendit, and bank transfer under Integrations → Payments.

REST API

Authenticate, paginate, and handle errors on the Planeward public API.

On this page

Open SettingsOwner and MemberBuilt-in rolesCreate a roleTurn permissions onWhat the groups coverGive a role to peopleFrom MembersFrom the roleProject access on topChat channels on topRole settingsView as a teammateWho can use itStart and exitIt's read-onlyGood to knowNext