> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/portal-overview/portal-admin-settings.md). # Admin Settings Managed by Peoplevine Some settings that affect the Member Portal experience are **not** configurable in the Control Panel and must be updated by Peoplevine. To enable, disable, or modify any of the settings below, contact your Account Manager or Support Team. This article is a quick reference for Peoplevine-managed settings only. Self-serve admin settings are configured separately in your Control Panel. ### Settings reference #### 1. Member Nomination Settings **Controls**: visibility of nomination data within the portal. **Options:** * **Hide All Nomination Data** — nominee records and statuses are completely hidden from members. * **Hide Nomination Status Only** — nominee profiles are visible, but the approval status is hidden. #### 2. Show Remaining Ticket Quantity **Controls**: whether members see a remaining ticket counter when ticket inventory drops below 10. **Behaviour:** * **Toggle ON** — shows the remaining ticket count once availability drops to 9 or fewer. * **Toggle OFF** — keeps *Tickets Available* displayed until the event sells out. > See [Events Engine — Overview](/products/control-panel-overview/events-engine-overview.md) for related ticketing behaviours. #### 3. Show Blog Post Dates **Controls**: whether the published date appears on blog posts. **Behaviour:** * **Toggle ON** — blog posting dates are visible to members. * **Toggle OFF** — dates are hidden from view. > Note that blog posts are still **ordered** by Posting Date regardless of this setting. See: [Portal Modules and Features — Overview](/products/portal-overview/portal-modules-overview.md). #### 4. Require Guest Email / Require Guest Mobile Number **Controls**: whether an email address and/or a mobile number is required when sending guest passes, sharing tickets, or booking for a guest. These are two separate toggles — enable either or both. > See [Guest Passes — Overview](/products/check-in-app-overview/guest-passes-overview.md) and [Events Engine — Overview](/products/control-panel-overview/events-engine-overview.md) for sharing behaviour. #### 5. Enable Public Registration **Controls**: whether non-members can use a public registration flow to create an account. This does not change how existing members log in. **Behaviour:** * **Toggle ON** — registration flow is enabled for non-members. Used to allow non-members to sign up for public events through the portal. See: [How to Set Up a Public Event](/products/control-panel-overview/events-engine-overview/setup-public-event.md). * **Toggle OFF** — registration is disabled; only CRM-listed members can access the portal. #### 6. Allow Failed Members to Pay Dues in Portal **Controls**: whether members with a failed membership status can use the Member Portal to pay their outstanding dues — i.e., whether the Failed Dues Paywall offers a **Pay Now** action or is informational only. **Behaviour:** * **Enabled** — eligible members see a Pay Now option to resolve their failed payment from the paywall. * **Disabled** — members see the failed status but cannot pay from the paywall (informational only). > The contact email shown on the Failed paywall is the email under **Company Profile > Contact & Social Information**. Sub-members never see Pay Now even when this is enabled — only the primary account holder can pay. See: [How Members Get Access to the Portal](/products/portal-overview/member-portal-access.md). #### 7. Legacy Events Redirect **Controls**: whether the old `/events` pages redirect to the new portal events experience. **Behaviour:** * **Toggle ON** — visitors to the legacy `/events` URL are redirected to the new events pages on the portal. * **Toggle OFF** — legacy `/events` pages remain accessible. > Use this setting when you have fully migrated to the new events experience and want to retire the old event pages. ### How to request a change 1. Email your Peoplevine Account Manager or open a Support ticket. 2. Specify the setting name and the value you want (e.g., *Show Remaining Ticket Quantity → ON* or *Enable Public Registration → OFF*). 3. Confirm the change is live by testing the relevant flow on your portal. ### Best Practice * **Decide on Enable Public Registration deliberately** — it shapes who can register from outside. If it's off, a public event link prompts unknown users to log in with no path to register. * **Keep Company Profile > Contact & Social email current.** That is the address members reach when they cannot self-resolve a Failed paywall. * **Match Show Remaining Ticket Quantity to your sales philosophy.** If you use scarcity to drive conversion, leave it ON. If you prefer a clean *Tickets Available* until sold out, turn it OFF. ### What Happens Next * **On the member side**: Once Peoplevine applies the change, members see the new behaviour on their next page load (no member-side action required). * **Next step**: [Member Portal — Overview](/products/portal-overview.md) · [How Members Get Access to the Portal](/products/portal-overview/member-portal-access.md) · [Events Engine — Overview](/products/control-panel-overview/events-engine-overview.md) · [Guest Passes — Overview](/products/check-in-app-overview/guest-passes-overview.md). *Last updated: 2026-07-12* --- # 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.peoplevine.com/products/portal-overview/portal-admin-settings.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.