--- title: "Members and Permissions" slug: "members-and-roles" status: "update" updated: 2026-10-03T03:05:27Z published: 2026-10-03T03:05:27Z canonical: "docs.revealdata.com/members-and-roles" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.revealdata.com/llms.txt > Use this file to discover all available pages before exploring further. # Members and Roles In Logikcull for Public Records, users are referred to as **members**. The ![members icon](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LPR_Members_Icon.png) **Members** tab shows which individuals have access to your agency, and allows you to add, edit, and deactivate members. Each member is assigned their own **role**, which determines their permission level in the platform: - **Admin** – Full access. Can configure agency settings, and view and manage all requests. - **Officer** – Manages assigned requests, updates statuses, notes, and assignments. - **Viewer** – Read-only access to requests. ## Team Members list The **Team Members** list, accessible from **Settings** > ![members icon](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LPR_Members_Icon.png) **Members**, shows all members who have been added to your agency's instance. Each row shows the member’s name and email, their current role, their status, and available actions. You can use the search bar to find members by name, email, or role, or filter the list using the **All Roles** and **All Status** dropdowns. ![](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LPR_Members_Sep26(1).png) Each member in your list has a status, which shows the state of their account: - **Active** – The member can sign in and access the platform according to the permissions in their role. - **Invited** – The member has been invited to the platform but has not accepted. - **Invite Expired** – The member has not accepted their invitation, and the invitation has expired. - **Deactivated** – The member has been manually deactivated. ### Add new member To add a new member to your agency… 1. Click **Invite User**. This will reveal an area to add your members. ![Input field for email address and role selection with a send invite button.](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LPR_Invite User_Sep26.png) 2. **Email address**: Type your member’s email address. 3. **Role dropdown**: Choose your member’s role. Descriptions of each role are at the very top of this article. 4. Click **Send Invite** to create your new member and invite them to your agency through email. The Team Members list also supports the following actions: - ### Change role - ### Deactivate member - ### Reactivate member - ### Resend member invite - ### Delete member invite **Change role** ### Change member role 1. Under **Name**, locate your member’s row. 2. Under the **Role** column, click the role dropdown. 3. Choose a new role for your member. **Deactivate member** ### Deactivate member Deactivated members will lose all access to logging in to your agency. To deactivate a member: 1. Under **Name**, locate your member’s row. 2. To the very right of the row, click ![deactivate icon](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LPR_Deactivate_Icon(1).png) **Deactivate**. **Reactivate member** ### Reactivate member Reactivated members will regain access to logging in to your agency. To reactivate a member: 1. Under **Name**, locate your member’s row. 2. To the very right of the row, click ![reactivate icon](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LPR_Reactivate_Icon.png) **Reactivate**. **Resend invite** ### Resend member invite 1. Under **Name**, locate your member’s row. 2. To the very right of the row, click ![resend invite icon](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LPR_Mail_Icon.png) **Resend invite**. > [!NOTE] > Note > > If you click Resend Invite before the current invitation has expired, the previous invitation will be deactivated. **Delete invite** ### Delete member invite 1. Under **Name**, locate your member’s row. 2. To the very right of the row, click ![delete invite icon](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LPR_Trash_Icon.png) **Delete invite**. Deleted invites will immediately deactivate the token present in the email, even if the invite hasn’t expired yet. ## Member settings From the Team Members list, click any member’s name to open up their **member settings**. Here, Admins can set Out of Office (OOO) dates, assign locations, or designate a member as a fallback assignee. ### Member information Admins can change the job title or phone number of any member. However, a member’s display name and image can only be changed by that member. To return to the Team Members list, click ![back to members icon](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LPR_Back arrow_Icon.png) **Back to members**. ![Profile information for a member including name, job title, email, and phone number.](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LPR_Member settings_Sep26(2).png) ### Out of office (OOO) status Admins can set any member as **out of office** and assign a delegate to receive rerouted requests. Each member also has the ability to set themselves as out of office through their profile settings. - For instructions on how to set members as out of office, see [Profile Settings](/logikcull-for-public-records/docs/profile#out-of-office). - For a diagram of how OOO delegates, locations, and fallback assignees impact request assignment, see [Routing Flow Chart](/logikcull-for-public-records/docs/routing-flow-chart). ### Set locations After adding locations to your agency, they can be assigned directly to members, which limit the requests they can view and claim. - Members with **no location** will only see requests that are assigned to them by an Admin or automated rule. - Members with **one or more locations** will only see requests from their locations, or requests that have been explicitly assigned to them by an Admin or automated rule. - Members with **Cross-Location access** will see all incoming requests, including requests that are in the **unassigned queue** (requests without a location). ![Options for selecting office locations and cross-location access settings are displayed.](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LPR_Locations_Sep26(1).png) For further information on how locations function in Logikcull for Public Records, see [Locations](/logikcull-for-public-records/docs/locations). ### Set fallback assignee The **fallback assignee** is designed to be the last-resort assignment for requests that do not trigger any of the routing mechanisms tied to routing rules, OOO assignees, delegates, and locations. Use the **Receives requests left unassigned** toggle to designate someone as a fallback assignee. Each agency can have only one fallback assignee at a time. Turning on the toggle for a new member automatically assigns them as the fallback and removes the previous member from that role. ![Settings for fallback assignee to receive unassigned requests in a user interface.](https://cdn.us.document360.io/3e21d801-ca9f-4c51-93db-9cbd32741f3d/Images/Documentation/LPR_Fallback assignee toggle_Sep26.png) > [!NOTE] > Note > > Fallback assignees are optional. If no one in an agency is designated as a fallback assignee, requests that fail all other routing rules will end up in the unassigned queue. ## Troubleshooting ### “Invalid activation token” message when trying to set my password. If you’re activating your account by setting your password and get an **Invalid activation token** message, it’s likely you’re encountering one of the following issues: 1. The invitation’s expiration window has passed. 2. Your admin resent your invitation, and you’re trying to log in through an old email. This could also happen if your admin accidentally sent a second invitation before the first invitation expired. 3. Your admin deleted the invitation, deactivating the token manually. Reach out to your Admin and ask them to resend your invitation. If you’re having further difficulties, email [support@revealdata.com](mailto:support@revealdata.com) for assistance.