ANTE User ManualProject Settings
The Project Settings page controls how the Projects module behaves across your whole organization. From one screen you set which view tabs a brand-new project starts with, how project codes are assigned when new projects are created, and how often your team is expected to interact with clients (which feeds each project's health score).
These settings apply module-wide, so a change here affects every project going forward.
Overview
The page has the breadcrumb trail Projects › Project Settings and the heading Project Settings ("Configure project module settings"). It is split into three cards, each with its own Save button:
- Views on a New Project — which tabs a newly created project starts with.
- Project Code Numbering — how new project codes are built.
- Client Interaction Frequency — the organization-wide target for client contact, used by Project Health.
All three cards share one underlying settings record, so clicking Save in any one of them saves every field on the page — the card you didn't touch is saved too, with whatever value it already held.
The same fields also open as a quick dialog: click the gear icon next to Templates on the Project List page header. The dialog has a single Save button at the bottom instead of one per card, but it saves the identical settings — use whichever is more convenient.
Views on a New Project
This card decides which view tabs a brand-new project starts with — including a project created from a template. Its description reads: "Which tabs every newly created project starts with."
| Tab | What it is |
|---|---|
| Project Tracker | A grouped task list with drag and drop. |
| Board | Kanban columns by status. |
| Gantt | A timeline chart by each task's start and due dates. |
Switch each tab on or off with its toggle. At least one tab must stay on — turning off the last remaining one is blocked, since a project with no tabs would have nothing to open.
This only changes what new projects get. Existing projects keep the tabs they already have; add or remove a tab from an existing project in its own Project Views.
Project Code Numbering
This card decides how a project's code is set when someone creates a new project. Its description reads: "Choose how project codes are assigned when creating new projects."
Choosing a mode
The Mode dropdown has two choices:
| Mode | What it means |
|---|---|
| Manual — enter code each time | The person creating a project types the project code themselves. |
| Auto — generate code automatically | The system builds the code from a prefix and a running number (for example, PRJ-001). |
When Manual is selected, the Mode dropdown is the only field in this card. When Auto is selected, four more fields appear along with a live preview.
Auto-numbering fields
These fields only show when Mode is set to Auto:
| Field | What it does |
|---|---|
| Prefix | The text that starts every code (example: PRJ). |
| Separator | The character placed between the prefix and the number (example: -). |
| Number Padding | How many digits the number is padded to with leading zeros — 2 (01), 3 (001), 4 (0001), or 5 (00001). |
| Next Number | The number the next new project will use; the system counts up from here. |
Next code preview
Below the fields, a Next code preview shows exactly what the next project code will look like, built live from your prefix, separator, padding, and next number. With prefix PRJ, separator -, padding 3 (001), and next number 1, the preview reads:
PRJ-001Change any field and the preview updates immediately, so you can confirm the format before saving.
How this affects new projects
The mode you pick changes the Project Code field on the new-project form:
- Auto mode — the Project Code field is filled in automatically (it shows the next code, with Auto-generated as its hint) and is locked, so it can't be edited. The system assigns the code when the project is saved.
- Manual mode — the Project Code field is open for typing and is required. You must enter a code before the project can be saved.
See Creating a Project for the new-project form itself.
Client Interaction Frequency
This card sets a single, organization-wide expectation for how often your team should be in contact with clients. Its description reads: "Set how often your team should interact with clients. This is used to calculate the Engagement score in Project Health."
Required Frequency (days) — the number of days within which the team is expected to interact with each client (example: 7). The helper text reads: "Projects without interactions within this many days will show a lower health score."
So if you set this to 7, any project that goes more than 7 days without a recorded client interaction shows a lower project-health (engagement) score.
This value is the global default for the whole organization. An individual project can override it for itself — when editing a project, leave the override empty to keep using this global default, or set a value to use a custom frequency for that project only.
Common Tasks
Change which tabs new projects start with
- Open the Project Settings page (or click the gear icon next to Templates on the Project List page).
- In the Views on a New Project card, turn tabs on or off — Project Tracker, Board, Gantt. At least one must stay on.
- Click Save. Projects created from now on — including from a template — start with the tabs you left on; existing projects are unaffected.
Switch project codes from manual to automatic
- Open the Project Settings page.
- In the Project Code Numbering card, set Mode to Auto — generate code automatically.
- Fill in Prefix (e.g.
PRJ), Separator (e.g.-), choose a Number Padding, and set the Next Number to start from. - Check the Next code preview to confirm the format.
- Click Save. New projects now get their codes generated automatically.
Go back to typing codes manually
- Open the Project Settings page.
- Set Mode to Manual — enter code each time.
- Click Save. The prefix, separator, padding, and number fields disappear, and the project code must now be typed in when a project is created.
Change where auto-numbering continues from
- Open the Project Settings page with Mode set to Auto.
- Update Next Number to the value you want the next project to use.
- Confirm the Next code preview, then click Save.
Tighten or relax the client interaction target
- Open the Project Settings page.
- In the Client Interaction Frequency card, change Required Frequency (days) to the number of days you want.
- Click Save. Project health scores use the new frequency when measuring engagement.
Saving and confirmation
Click the Save button inside whichever card you changed. On success you see the message "Project settings saved". If saving fails, the message reads "Failed to save project settings".
The three cards save together — after changing a setting in any card, click the Save button in that card and wait for the "Project settings saved" confirmation before leaving the page.
Related Pages
- Project Views — where a project's own view tabs are added or removed after it's been created.
- Creating a Project — where the project code (auto or manual) is applied.
- Engagements — recorded client interactions that feed the engagement score.
- Project List — where you open or create projects, and where the gear icon offers this same page as a dialog.
- Projects (Workspace) Module — overview of the whole module.
💡 Note: These settings are organization-wide. Setting them is normally handled by a Project Manager, Operations Manager, or Administrator — if you can't open the page or save changes, contact your administrator.
How It Connects
Feeds into
- Project List — the gear icon next to Templates opens these same settings as a quick dialog.
- Project Views — the tabs enabled here are what a newly created project's Views start with.
- Creating a Project — the code numbering mode decides whether the Project Code field is typed or auto-generated.
- Project Details (Project Health) — the client interaction target feeds each project’s health score.