Product

Private features

A feature is open to everyone in your workspace until you make it private. Then only the teams you choose can see it, with everything under it, and each team gets Can view or Can edit. The teams are your organization's teams, from Teams.

The people who manage the workspace can always see and edit every private feature, so nothing can be locked away from them. They are every Owner and Admin of your organization, the workspace's owner, and its admins. See Workspace settings.

Sees the featureCan change it
A member of a team with Can editYesYes, even if their role is Viewer or Customer
A member of a team with Can viewYesNo, whatever their role allows
Someone who manages the workspaceYesYes
Anyone elseNoNo

Changing a feature covers its title and other fields, its document, status, priority and assignees, its links to applications, services and other features, its business rules, and reviewing proposed changes to its specification. Deleting the feature, adding subfeatures to it, and starting AI work on it (refreshing its specification from the code, composing it from its components, generating tasks, sending comments to the agent in Review mode, chatting with the code) also need your role to allow them: Can edit alone isn't enough. Anyone who can see the feature can comment on it if their role allows.

You make a feature private, or change who can see it, in the Productmind app only. The AI Assistant, coding sessions, the Productmind CLI, AI assistants you connect over MCP and your own tools that call the API can't change it.

To make a feature private

  1. Open the feature, and choose Access in its header.
  2. Choose Only these teams.
  3. Choose Add team, then choose a team.
  4. Choose what the team can do: Can view or Can edit.
  5. Repeat steps 3 and 4 for each team that should see the feature.
  6. Choose Save. If subfeatures under it have teams of their own, Productmind asks about them first: see When subfeatures have teams of their own.

The feature is private: only the teams you chose, and the people who manage the workspace, can see it and everything under it. A lock in its header, and on its row in the Features list, shows that it's private. See How private features behave for what everyone else sees.

Unless you manage the workspace, keep a team you belong to with Can edit. Productmind doesn't let you take away your own access to edit the feature.

To change what a team can do

  1. Open the feature, and choose Access in its header.
  2. Next to the team, choose Can view or Can edit, or choose Remove to take the team off the list.
  3. Choose Save. If subfeatures under it have teams of their own, Productmind asks about them first: see When subfeatures have teams of their own.

The change applies as soon as you save. Members of a team you removed no longer see the feature, unless another of their teams is on the list or they manage the workspace.

To make a feature open to everyone again

  1. Open the feature, and choose Access in its header.
  2. Choose Everyone in this workspace.
  3. Choose Save.

Everyone in the workspace can see the feature again. If a feature above it is private, the choice reads Same as that feature instead, and the feature stays private with that feature's teams: open Access on that feature to change them.

When subfeatures have teams of their own

When you choose Save in Access and subfeatures under the feature have teams of their own that you can change, Productmind asks what should happen to them first:

  • Keep their own lists leaves them as they are. They keep narrowing who can see them, and deciding who can edit them.
  • Make them follow, followed by the feature's name, removes their own lists, so who can see and edit them follows the feature's teams.

Keep their own lists is always selected first. To make them follow, type Confirm in the box, then choose Save. Cancel takes you back to Access without saving anything.

A subfeature keeps its own list either way when you can't change it, or when its list is what lets you edit it: Productmind doesn't let you take away your own access to edit a subfeature. The question says how many subfeatures keep their lists for those reasons.

How private features behave

Everything under a private feature is private too, with the same teams. A subfeature can have teams of its own to narrow who sees it: to see a subfeature, you need a team on its list and on the list of every private feature above it. What a team can do with a subfeature comes from the nearest list, its own or the one above it, so a team with Can view above can have Can edit on the subfeature.

For anyone who can't see it, a private feature doesn't exist. It isn't in the Features list, the Feature map, search or the dashboard, and a link to it says that the feature wasn't found. The tasks, sessions and bug reports under it stay visible to them, with Private feature in place of the feature's name.

Nobody is told about a feature they can't see. Mentions, assignments and emails about a private feature reach only the people who can see it. When you type @ in a comment on a private feature, people who can't see it are grayed out with No access, and you can't choose them. A comment that names them anyway keeps their name as plain text and notifies nobody. Productmind doesn't post private features to your Slack channel, changes to them don't trigger automations, and release notes that Productmind generates leave them out.

AI works as you. The PM agent and the AI assistants you connect over MCP find only the features you can see, and a coding session sees what the person who started it can see. Scans and other work Productmind does on its own still keep a private feature up to date, without showing it to anyone else.

Review mode and code chats follow the teams. With Can view, you can comment on a private feature, but you can't send the comments to the agent or start a code chat about it. A component under the feature with teams of its own, which narrow who can see it, is left out of a review or a code chat about the feature: the agent isn't pointed at it, and a code chat can't propose changes to it. See Review mode on specifications and Code conversations.

A code chat never shows a private feature's title. Its name shows the feature's ID, such as FEAT-12, instead. The chat itself is private to the person who started it, and of your Productmind workspace the agent sees only what that person can see.

Moving a feature can change who sees it. You need to be able to change both the feature and its new parent. Moving a feature into or out of a private feature also needs the right to change who can see it. See Permissions.

Deleting needs to see everything under the feature. You can't delete a feature that holds a private feature you can't see. Ask someone who manages the workspace to delete it.

A deleted team keeps a feature private. If a team on the list is deleted, the feature stays private. In Access, the people who manage the workspace see it as Deleted team, and can remove it.

Team changes apply within about 30 seconds. Adding someone to a team on the list shows them the feature, and removing them from the team hides it. A private feature also stays private if your organization's plan changes.

What was sent before stays as it was. Notifications, emails, Slack messages and release notes sent before a feature became private keep what they said.

Permissions

A private feature's teams change the permissions every feature needs (see Features), on that feature and everything under it:

  • To see it, you also need a team on its list, or to manage the workspace.
  • To change it, Can edit is enough, even without Features: Update. With Can view, you can't change it, whatever your role allows.
  • To delete it, add subfeatures to it or start AI work on it, you need Can edit and the permission your role needs for it on any feature. Sending comments to the agent in Review mode needs Features: Update, and chatting with the code needs Sessions: Create; for a code chat's agent to propose a correction, the person who started the chat also needs Features: Update.
  • People who manage the workspace can see and change every private feature, whatever their role, and change who can see it. Deleting it, adding subfeatures and AI work still need the permission your role needs for them.

The people who manage the workspace are an Owner or Admin of your organization, the workspace's owner, and its admins.

Troubleshooting

The feature, or a feature above it, is private, and you aren't on any of its teams. It may also have been deleted. Ask someone who can edit the feature, or who manages the workspace, to add a team you're on. See To make a feature private.

I can't change a feature that my role lets me change

The feature is private, and your team has Can view on it. Ask someone who can change who sees the feature to give your team Can edit.

I can't send comments to the agent, or chat with the code, on a private feature

Your team has Can view on the feature, which leaves out AI work whatever your role allows. You can still comment, if your role allows. Ask someone who can change who sees the feature to give your team Can edit, or ask someone who can edit the feature to send the comments.

"You would lose access to edit this feature"

The change would leave you without Can edit on the feature. Keep a team you belong to on the list with Can edit, or ask someone who manages the workspace to make the change.

"This feature contains private features you do not have access to"

Something under the feature is private, and you can't see it, so you can't delete the feature. Ask someone who manages the workspace to delete it.

"Moving this feature changes who can see it"

You're moving the feature into or out of a private feature, which changes who can see it, so you need the right to change who can see the feature. See Permissions, or ask someone who manages the workspace to move it.

Last modified on