Positions

Flowtly Editorial Team2 min

Positions, found under Settings → People → Positions, is where administrators manage the job positions within their organization. This feature allows you to define and maintain a standardized list of roles.

Use the Add position button to create a new role. Existing positions can be modified by selecting the position from the list and choosing the edit option, or removed if they are no longer needed.

Defining positions helps maintain consistency in job titles across the company. These standardized positions can then be applied to individual employee records and are utilized in various reporting functions, ensuring accurate and uniform data across the platform.

Choosing a position elsewhere in the app

Wherever a position is chosen — on an employment agreement, or on a project rate — you pick it from this shared list rather than typing it. Start typing to filter the list, then select the position you want. Typing a name on its own never creates a position, so a small typo cannot quietly add a near-duplicate such as "Senio React Developer" alongside "Senior React Developer".

If the role you need genuinely does not exist yet, choose Add new position at the bottom of the list. This is available to administrators with the positions permission; if you do not see it, ask an administrator to add the position for you, or create it here on the Positions page.

When the name you type differs from an existing position only by capitalization or spacing — for example "DEV OPS" against "DevOps" — a note appears pointing at the existing one. Select that instead of creating a second entry: two positions meaning the same thing split your reporting between them.

Keeping the list tidy

A position cannot be deleted while anything still points at it — an employment agreement, a resourcing allocation, or a project rate. Reassign those to the position you want to keep first, and the delete will then succeed. This is deliberate: it stops a position disappearing out from under records that depend on it.

Example use cases

  • Standardize job titles for new employees during the onboarding process to ensure consistent terminology.
  • Generate accurate reports on team structures and departmental organization based on assigned positions.
  • Update a position's official title or description, ensuring the change is reflected consistently across all employees assigned to that role.
  • Deactivate or remove obsolete positions that are no longer in use within the organization.

Connection map

Refers toPart of
Documented hereDocumented elsewhere
audit-log records person. setting defines attribute. org-document access governed by setting. subscription gates setting.recordsdefinesaccess governed bygatesAAudit trail — The record of who did what and when. It is how a user action is investigated after the fact, and what compliance is demonstrated from.Audit trailPPerson — An employee. The central record the rest of the workforce data hangs off — profile, documents, leave, benefits, rates.PersonSSetting — Platform-wide configuration — behaviours, permissions, security.SettingAAttribute — A custom data field defined once and collected across the platform, so an organisation can record what Flowtly does not ship a field for.AttributeDDocument — An organisational file, stored with control over who can reach it.DocumentSSubscription — The plan the organisation is on, and what it is billed for.Subscription