> ## Documentation Index
> Fetch the complete documentation index at: https://docs.officeridge.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Projects

> Track agency projects with meetings, requirements, and stakeholder contacts.

Projects holds your agency's project portfolio with meetings, requirements, and stakeholder contacts.

Use it for work that is not day-to-day care delivery: opening a new location, adding a service line,
implementing a system, or preparing a major initiative.

## Who can use it

Organization Admins, Location Admins, Clinical Managers, and Client Coordinators.

## Tabs

<AccordionGroup>
  <Accordion title="Projects" icon="clipboard-list">
    Project portfolio with status, priority, access controls, timelines, and completion percentages.

    **Columns:** Name · Status · Priority · Owner · Access · Start · End · % Done

    Opening a project also exposes its description, team, and a **Contains PHI** marker.
  </Accordion>

  <Accordion title="Meetings" icon="calendar">
    Meeting records with type classification and scheduling details.

    **Columns:** Name · Type · Start
  </Accordion>

  <Accordion title="Requirements" icon="list-checks">
    Project requirements with type, priority, and implementation status.

    **Columns:** Name · Type · Priority · Status
  </Accordion>

  <Accordion title="Contacts" icon="contact">
    Project stakeholder links to the Contacts collection — members, physicians, and staff — with
    roles.

    **Columns:** Name · Contact · Role · Phone · Email
  </Accordion>
</AccordionGroup>

## Access and PHI on projects

Projects carry two controls that most modules do not:

* **Access** limits who can open the project, separately from the module-level role gate.
* **Contains PHI** marks a project whose materials include protected health information.

<Warning>
  Set **Contains PHI** whenever a project's documents or notes reference identifiable member
  information. Marking it correctly is what keeps a project out of the wrong hands — the field is
  not decorative.
</Warning>

## Running a project

<Steps>
  <Step title="Create the project">
    Set a name, owner, priority, and start and end dates. Mark **Contains PHI** if it applies.
  </Step>

  <Step title="Capture requirements">
    Break the work into requirements on the **Requirements** tab, each with a type and priority.
  </Step>

  <Step title="Add stakeholders">
    Link people on the **Contacts** tab with their role on the project.
  </Step>

  <Step title="Record meetings">
    Log meetings as they happen so the decision trail stays with the project.
  </Step>

  <Step title="Track completion">
    Keep **% Done** current. It is what the portfolio view reports against.
  </Step>
</Steps>

<Tip>
  Contacts on a project link to existing records rather than creating new ones. Add the physician or
  staff member to the underlying directory first, then link them here.
</Tip>

## Troubleshooting

| Problem                                  | What to check                                                                                       |
| ---------------------------------------- | --------------------------------------------------------------------------------------------------- |
| A colleague cannot see a project         | The project's **Access** setting may exclude them, even if their role permits the Projects module.  |
| A contact I want is not selectable       | Contacts link to existing records. Create the person in the relevant directory first.               |
| Requirements are not rolling into % Done | **% Done** is set on the project. Update it as requirements complete.                               |
| Projects is missing from my sidebar      | Your role does not include it. See [Roles and permissions](/getting-started/roles-and-permissions). |

## Related

<CardGroup cols={2}>
  <Card title="Task Manager" icon="list-checks" href="/tasks">
    Recurring tasks and weekly completion rollups.
  </Card>

  <Card title="CRM" icon="contact" href="/crm">
    Contacts, calls, encounters, and tickets.
  </Card>
</CardGroup>