Getting Started
How the platform fits together
Understand people, projects, records, permissions and the difference between internal and internet publishing.
ExplanationFor all workspace membersContent reviewed
On this page
People and organizational context#
A workspace holds the organization's work and people records. Departments group responsibilities. Roles and permissions decide which operations a person can attempt, while record-level scope can further restrict which data they can use.
A designation describes a position and can affect pay or costing configuration. A reporting relationship identifies management context. Neither should be treated as a universal permission grant.
Projects and delivery#
| Record | Purpose |
|---|---|
| Project | Groups delivery scope and related work. |
| Story | Describes a requirement and acceptance criteria where the project uses stories. |
| Task | Holds an actionable piece of work, ownership and progress. |
| Sprint | Organizes an iteration of delivery work where enabled. |
A project can use a simpler workflow without every planning surface. Select the structure that is actually available in that project. Create a task explains the creation form.
Time and payroll#
Attendance records the working day. Leave records time-off requests and decisions. Task time records activity against work. These are related inputs, but they are not interchangeable proof that payroll is ready.
Payroll preparation reviews the period, employee inputs and blockers. Approval and payment have their own authorities and completion evidence. Follow the handoff.
Documents and audiences#
| Term | Meaning |
|---|---|
| Private or scoped document | Its audience is restricted by the applicable access rules. |
| Internal public visibility | Broad visibility inside the company, not internet publication. |
| Document review | An assigned reviewer evaluates a document. |
| Website guide | Content eligible for the separate public publishing process. |
A document being readable does not necessarily mean that you may edit, change its audience or delete it. Read Document permissions or Website publishing.
AI and source records#
WorxAI can help locate and interpret accessible information. Its response is not a replacement for the original task, request or pay record. Check source records and confirm a supported action before it runs.
Why two people see different controls#
An action may depend on the feature being enabled, a component permission, organizational scope, record access and the current workflow state. Ask about the exact missing action and record rather than relying on the name of a role.
Need more help?
Can’t find what you need? Talk to the team.
To report a problem with this guide, include its title and the step that blocked you.