Core concepts

A few building blocks show up everywhere in Helpin. Once you know how workspaces, teams, members, roles, and modules relate to each other, the rest of the product is easier to navigate.

Workspace

Your workspace is the shared home for your organization. It holds your members, their roles, and organization-wide controls such as security, billing, audit, and integrations. Everything your teams create — tasks, conversations, deals, documents, and automations — lives inside it.

Your data never crosses workspace boundaries: it is not shared with other workspaces.

Teams

Teams group the people who plan and deliver work together. A team belongs to one workspace; creating a team does not create a separate workspace.

Each team has its own settings for how it works — members and owners, a team handle (for example @growth) that people can mention, labels, workflows and statuses, templates, automations, and PM defaults. Workspace-wide rules stay in workspace settings. See Teams.

Team membership also shapes what you see. For example, My Work shows tasks from the teams you belong to, and a team-only Docs space is visible only to its selected teams.

Members and roles

Members are the people in your workspace. Each member has a workspace role that controls what they can do:

• Viewer — can read, but not edit.

• Member — can read and edit, and publish internally.

• Admin — can also manage administration settings.

• Owner — has the same capabilities as an admin.

Workspace administrators and owners manage members, invitations, and roles. The exact capabilities of each role are described per module — for example, Docs access & sharing.

Modules

Helpin's modules are Projects (PM), Support, CRM, Docs, and Automation. Projects and Docs are available to every member. Module access decides whether a member also sees CRM, Support, and Automation in the sidebar; owners and admins always have every module. It works alongside roles:

• Module access is the visibility gate — if someone isn't granted CRM, Support, or Automation, that module doesn't appear in their navigation.

• Role permissions are the capability gate — they decide what someone can do inside a module they can see.

For example, a support team may need Support but not CRM. See Module access control.

Agents and flows

Automation in Helpin comes in two forms. Flows automate repeatable steps, such as creating or updating a document. Agents are AI teammates that plan, build, triage, follow up, and update documentation. Agents can act autonomously or with human approval, share context, and escalate to a person when needed.

Next steps

Ready to set things up? Continue to Getting started.