> For the complete documentation index, see [llms.txt](https://help.fielddoc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fielddoc.org/account-management/user-account/user-roles.md). # User Roles ## Organizations Stewarding data for an organization is a multi-person, multi-year effort so it's important that data is accessible across an organization and not limited to single-viewer accounts. FieldDoc organizations represent real-world entities, such as companies or non-profits, whose employees and/or volunteers manage data using the platform and its associated tools. All data and activities in FieldDoc are linked to an organization. As the users within an organization change over time, the data remains constant. All users within an organization are categorized as standard or general users. All users are assigned to an organization, regardless of their user type or role. *** ## User Types ### Standard Users Standard FieldDoc users can create a portfolio of activities and metrics, collaborate on activities created by other users, or share their activities through a Pact. Users are associated with an organization, which allows all members to view records within that organization. If you're using FieldDoc for grant reporting, a Standard account is required. Within an organization, users can be assigned either Admin or Read-Only access to a portfolio. {% hint style="info" %} ### At Registration Upon registration, all FieldDoc users start with **Standard** access. Through the registration process, you'll complete your standard account setup. Once you have created an account and assigned yourself to your organization, you will be able to add, edit, and delete data within your organization's portfolio. If you would like to upgrade your account to one of the user types listed below, please reach out to for assistance. {% endhint %}
Organization/pages/tbdSBOvHRPkpL9fKkFIw
Workspaces/pages/wnEQnufXPb0BGpA1iojB
### Technical Service Providers This work is nothing if not a team effort! We want to make sure that your full team — both within your organization and those outside of it — can access the relevant information in FieldDoc. Collaborators are **Standard** users that have been given access to a **Workspace**, **Project**, **Pact**, or **Activity** outside of their organization. Collaborators are often Technical Service Providers (TSP) who support a grant recipient on everything from data management to sharing of detailed engineering designs. Collaborators looking to use FieldDoc to support their partners and clients must configure their own organization and a standard user account, just like the organizations that they are service - even if you are only working with one other organization in FieldDoc. Your collaborators can add you to their workspaces or projects *after* you have created your account.
Collaboration/pages/HrcOJTtykilgmJakRZYI
### Funding Program Managers Programs hosted in FieldDoc have a curated list of **activity types**, metrics, models, and target outcomes. Programs collect Activities from their constituents via Pacts. Program Managers are assigned by FieldDoc staff to the Program(s) that they manage. Once we configure a Program Manager account, that user can see all **Pacts** assigned to their program. *** ## User Roles FieldDoc offers two types of user roles: **Admin** and **Viewer**. These roles are available at various entry points, including **Organizations**, **Workspaces**, **Projects**, **Pacts**, and **Activities**. This enables you to share and collaborate on FieldDoc records at your preferred scale. For example, you may work with a contractor who needs broad access to your workspace. Adding that person as a Workspace Admin will grant them full permissions on all Project, Pact, and Activity records within your workspace (but *not* your organization settings). By contrast, sometimes you might need to invite a third-party to assist on a *subset* of your Activity records. In that case, a sound approach is to add those activities to a Project and share the Project with one or more of your external collaborators. ### Organization #### Admin Organization Admins have unrestricted access to an organization’s data and settings. They can add, modify, and delete records (e.g. projects, activities, metrics, pacts) and members. #### Viewer Organization Viewers have read-only access to an organization’s data and settings. Users assigned the Viewer role will **not** be able to edit or delete any records within their organization's account. ### Workspace #### Admin Workspace Admins have **unrestricted** access to a workspace’s data and settings. They can add, modify, and delete records (e.g. projects, activities, metrics, pacts) and members within the workspace. #### Viewer Workspace Viewers have **read-only** access to a workspace’s data and settings. Users assigned the Viewer role will **not** be able to edit or delete any records within the workspace. ### Project #### Admin Project Admins have **unrestricted** access to a project’s data and settings. They can add, modify, and delete records (e.g. projects, activities, metrics) and members within the project. #### Viewer Project Viewers have **read-only** access to a project’s data and settings. Users assigned the Viewer role will **not** be able to edit or delete the project or any records that it contains. ### Pact > #### 🚧Pact roles **do not** have access to the pact's **program-level**, **workspace-level**, or **organization-level** members or other settings. #### Admin Pact Admins have **unrestricted** access to a pact’s data and settings. They can add, modify, and delete records (e.g. activities, metrics) and members within the pact. #### Viewer Pact Viewers have **read-only** access to a pact’s data and settings. Users assigned the Viewer role will **not** be able to edit or delete the pact or any records that it contains. ### Activity #### Admin Activity Admins have **unrestricted** access to an activity’s data and settings, including collaborators, metric values, and all activity metadata. #### Viewer Activity Viewers have **read-only** access to an activity’s data and settings. Users assigned the Viewer role will **not** be able to edit or delete the activity or any records that it contains (e.g. files, metric values, model outputs). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.fielddoc.org/account-management/user-account/user-roles.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.