Team policy
How the owner or an admin restricts what members can do — editing and deleting tasks, GPS tracking, visibility of sections
Team policy is a set of restrictions the owner or an admin sets for the members of their team. With it you can forbid members to create, edit and delete tasks, change their status, log time manually, start GPS tracking or the timer, and hide individual app sections from them (mileage, reports, statistics, geofences).
The restrictions apply only inside a team organization and only to the tasks of its trackers. A member's personal work and trackers they connected personally are not affected by the policy.
What it is NOT
Team policy is a managed profile, not protection against workarounds. It configures the app interface but does not lock the data in the tracker:
- A member can still open the same Redmine (or another tracker) in a browser and edit the task there — the app does not control that.
- The real barrier against edits is the tracker's own permissions (roles in Redmine, permissions in OpenProject and so on). Team policy only removes the corresponding buttons in the app on top of them.
The point of the policy is to keep order in the app, so that a field employee does not accidentally delete a task or overwrite someone else's fields — not to build a security wall. If you need a hard restriction, configure permissions in the tracker itself.
Some restrictions are still enforced strictly, on the server: GPS tracking, moving a connector between teams, and writing the policy settings themselves. Taskloc really controls these points.
What you can restrict
| Action | Default for a member |
|---|---|
| Editing a task — title, description, priority, assignee, tracker | Forbidden |
| Creating a task — the "+" button on the task list | Allowed |
| Deleting a task | Forbidden |
| Changing the status of a task | Allowed |
| Manual time entry | Allowed |
| Timer without GPS | Allowed |
| GPS tracking | Allowed |
| Sections: mileage, reports, My stats, geofences | Shown |
Important about editing and deleting. By default, team members cannot edit or delete the tasks of this team's trackers until the owner or an admin explicitly allows it. This is intentional: a field employee sees the task, tracks it and changes its status, but does not rewrite its fields. The owner and admins are not affected by this restriction.
The restrictions are shared by the whole team: one set of rules applies the same way to every member and to every tracker linked to this team.
What a member sees
A forbidden action does not just silently disappear — the member understands that it is a team restriction, not a malfunction:
- The buttons and menu items of forbidden actions are hidden. If a member still tries to perform the action in a roundabout way, the message "Action is not allowed by organization policy" appears at the bottom of the screen.
- Personal toggles controlled by the team (for example, the master GPS toggle in the tracking settings) are shown turned off with the caption "Restricted at the organization level".
- Hidden sections (mileage, reports, statistics, geofences) are simply not shown while the member works in the context of this team. In the personal organization the sections are always there.
Who it applies to
- Only team members. The owner and admins are not restricted by the policy — they can always edit, delete and configure.
- The restrictions are tied to the team's trackers. If a member connected a tracker personally (to "Personal" or without linking it to a team), the policy does not apply to it — the team controls only what belongs to the team.
How to configure it (owner or admin)
- Open Manage organizations → your team's card.
- Go to the Policy tab.
- Turn the toggles for the actions and sections you need on and off.
Changes are saved immediately. You can configure the policy only for the active team — if you are in another context, the app will suggest switching to the right team.
You cannot turn on forced GPS (in the tracking settings) and forbid GPS (in the policy) at the same time — these settings are mutually exclusive, and the app will not let you save such a combination.
Limits on parallel sessions
Besides the policy toggles, a team has limits on simultaneous sessions — how many GPS sessions and how many timers one member can run in parallel. The limits are set separately for GPS and for timers (from 1 to 3 each; by default 1 GPS session and 1 timer) and are counted for the team the task's tracker is linked to.
An important difference from the rest of the policy: the limit applies to everyone, including the owner and admins — a role cannot bypass it. How the limit looks in practice is described in GPS tracking.
Moving a connector out of a team
There is an important consequence. If a member linked their own tracker to a team, they cannot take it back without an admin: moving a connector out of a team organization is allowed only to the owner or an admin of that team. This way the policy cannot be dropped simply by unlinking the tracker. More about connecting trackers — in Connectors.