--- title: "Member Settings" slug: "member-settings" updated: 2026-11-04T20:57:41Z published: 2026-11-04T20:57:41Z canonical: "docs.revealdata.com/member-settings" --- > ## 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. # Member Settings From the [Team Members](/logikcull-for-public-records/docs/members-and-roles) list, click any member’s name to open up their **member settings**. Here, Admins can set an individual member’s Out of Office (OOO) dates, assign them locations, or designate them 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.