> For the complete documentation index, see [llms.txt](https://docs.tiny.plus/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tiny.plus/guides/everyday/confidential-and-health.md). # Confidential records and health Keep a sensitive project to its team with the confidential flag, and read the health rating that shows which projects and clients are going quiet. ## Confidential records Some work can't be seen by the whole firm: a bid under a non-disclosure agreement, a client who hasn't gone public. Tick **Confidential?** on the project and tiny+ keeps it to the people on it. ### Who can see a confidential record The people assigned to it, on its team or following it, whoever created it, and Records Admins. Account Admins are Records Admins too. ### What everyone else sees As little as possible. The record is left out of the board when it shows everyone's records, out of the firm-wide tables, out of search and Ask, out of the News Feed, and out of the API. Where it does appear, in a list of someone's own records for instance, its name reads *(Confidential Project)* and its details are hidden. Opening it shows only the team and a note to ask them. Nobody can join its team from the page; someone on the team has to add them. The [search box](/guides/everyday/search.md) leaves confidential records out for everyone but Records Admins, so the team reaches theirs from the board or their own lists. [Scheduled reports](/guides/reports/scheduled-reports.md) are built for each reader from what they can open, so a confidential project never reaches someone who can't see it, and a report posted to the feed leaves confidential records out altogether. ### Posts on a confidential record A post on a confidential project stays on the project's own feed and is seen only by the people who can open it. It's never shared to the News Feed, nobody is notified of it, and it can't be liked, commented on or pinned. tiny+ writes none of its automatic posts about a confidential record. Separately, any post can be a **confidential note**, visible only to its author and the Account Admins. ### Companies and contacts The confidential flag is a field, so an Account Admin can add it to the company and contact forms in the [Form Designer](/guides/admin/fields-forms-and-panels.md). A confidential company's name is hidden on the projects and contacts linked to it.
A confidential project's page as seen by someone not on its team: the team, and a note to contact them for details
## Health Every project in your pipeline, and every prospect and client company, has a **health** rating. It's a way of seeing at a glance what's being looked after and what's slipping. A record starts at 100 and loses points the longer it goes without an update. With the standard rules it loses 10 points after 14 days, 20 more after 30, 20 after 60, 20 after 90, and the rest after 100 days. From 66 it shows green, from 33 amber, and below that red. An update is anything that touches the record: editing its fields, a post on it, a task or meeting added to it, an email filed against it, a picture. Pressing a button doesn't count. A company on a [relationship plan](/guides/everyday/relationship-plans.md) is scored from its last logged contact instead, once it has had one, so editing the company's details doesn't make a neglected relationship look healthy. ### Where it shows * On the [board](/guides/everyday/pipeline-board.md), as the coloured edge of each card, with the score and the reason on hover. Filter the board by health, or sort it worst first. * In tables and reports, as the **Health** column. * In the **Going quiet** section of a scheduled report, which lists the clients in poor health, and in the **Clients** section beside each client. * Through the API, when asked for. The board's score is worked out as you look. The score in tables and reports is updated once a day, so it can be a day behind. ### Your firm's rules An Account Admin sets the rules under [Account Settings -> Pipelines](/guides/getting-started/designing-your-project-pipeline.md). The **Health across the pipeline** card holds the rules for the whole pipeline, and each status or phase can have its own under its settings: a proposal might be allowed 14 quiet days before it loses points, an active project 30. Statuses that aren't rated, such as completed and lost projects, carry no health.