> For the complete documentation index, see [llms.txt](https://portavi.gitbook.io/portavi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://portavi.gitbook.io/portavi-docs/settings/workspace-settings.md).

# Workspace settings

**Settings → General**, for PMO managers.

<figure><picture><source srcset="https://4189291014-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx6fERvLd0cQQBYlynE5O%2Fuploads%2Fgit-blob-64c696e3ca9d79cf52b3b6912c28cbc21d97c8f4%2Fsettings-general-dark.png?alt=media" media="(prefers-color-scheme: dark)"><img src="https://4189291014-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx6fERvLd0cQQBYlynE5O%2Fuploads%2Fgit-blob-ccc00df1f3b3d1e20e30a5f63f630b9a5b0bf1b7%2Fsettings-general.png?alt=media" alt=""></picture><figcaption></figcaption></figure>

## Identity

* **Workspace name**
* **Logo**: upload one, and a **Remove logo** button appears once set
* **Workspace ID**: with a copy button, next to the name. Support may ask for it

## Regional

* **Timezone**: used for dates throughout
* **Currency**: used for every budget in the workspace. Detected from your region at signup

{% hint style="info" %}
All budgets in a workspace share one currency. Portavi does not convert between currencies, so choose the one you report in.
{% endhint %}

## Sync

**Default sync frequency**: how often integrations pull, unless a specific integration overrides it. The shortest is one hour.

**Working days & hours**: the days and hours automatic syncing runs, in the workspace timezone. Outside them scheduled syncs pause; manual sync always works. Set from your region at signup (Sunday–Thursday where that is the standard week), and editable here.

## Categories

Your workspace's own category list, used for tagging projects and grouping them on the Overview board.

* Up to 15 categories
* Each has a name and a colour from a fixed palette

{% hint style="info" %}
The palette deliberately excludes green, amber, red and blue: those already mean on track, at risk, delayed and completed elsewhere in Portavi, and reusing them for categories would make two different things look the same.
{% endhint %}

Deleting a category that projects are using prompts you to reassign or clear it first.

## Health thresholds

The workspace defaults deciding when projects turn amber or red. Individual projects can override them. See [Health statuses](/portavi-docs/tracking-delivery/health-statuses.md).

## Flagged items

Your workspace's custom flags: what else, besides the built-in rules, marks a task as needing attention. They run on every project unless a project switches one off. See [Custom flags](/portavi-docs/tracking-delivery/custom-flags.md).

## Signal keywords

The words Portavi watches for in connected chat channels, grouped by signal type: blocker, delay, urgency, issue, progress. Tune these to how your teams actually write. See [Communication tools](/portavi-docs/connecting-your-tools/communication-tools.md).

## Synced members

People pulled from your integrations. The same human often appears more than once (a Jira account and a Slack account) and you can **combine** those identities so capacity planning and reports count them as one person.

## Archive

See [Archiving and restoring](/portavi-docs/organising-your-work/archiving.md).