> For the complete documentation index, see [llms.txt](https://docs.xorosoft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xorosoft.com/xoroerp-1/admin/user/portal-user/portal-user-centre.md).

# Portal User Centre

The Portal User Centre serves as a comprehensive dashboard for managing customers who are designated as portal users within their customer profiles. This module provides administrators with the ability to oversee, update, and perform actions related to portal users, ensuring seamless interaction and account management for customers utilizing the B2B portal.

### Understanding Portal User Centre

The Portal User Centre serves as a dedicated space for tracking and managing all customers marked as portal users in their respective customer profiles. This includes essential information related to their accounts, login activities, and user status.

#### Portal User Centre Fields

<table><thead><tr><th width="174">Field</th><th>Description</th></tr></thead><tbody><tr><td>Customer</td><td>This field displays the name of the customer associated with the portal user account.</td></tr><tr><td>User Name</td><td>This field shows the username used by the customer to log into the portal.</td></tr><tr><td>Account #</td><td> This field displays the unique portal account number associated with the customer.</td></tr><tr><td>Portal Email</td><td>This field indicates the email address used for portal access.</td></tr><tr><td>Invitation Email</td><td>This field shows the email address to which the portal invitation was sent.</td></tr><tr><td>Invite Pending?</td><td>This field indicates whether the portal invitation is still awaiting acceptance. (Yes/No)</td></tr><tr><td>Currency</td><td>This field shows the default currency associated with the customer account.</td></tr><tr><td>Customer Email</td><td>This field shows the primary email address associated with the customer account.</td></tr><tr><td>User Id</td><td>This field shows the unique ID associated with the portal user.</td></tr><tr><td>Is Active?</td><td>This field indicates whether the portal user’s account is active.</td></tr><tr><td>Last login attempt?</td><td>This field displays the date and time of the most recent login attempt.</td></tr><tr><td>Create Datetime</td><td>This field displays the date and time the portal user account was created.</td></tr><tr><td>Created By</td><td>This field lists the name of the user that created the portal user record.</td></tr><tr><td>Modified Datetime</td><td>This field indicates the date and time when the portal user record was last modified.</td></tr><tr><td>Modified By</td><td>This field displays the name of the user who last updated the portal user record.</td></tr><tr><td>Is Email Verified?</td><td>This field shows whether the portal email address has been verified.</td></tr></tbody></table>

#### Portal User Centre Options

* **Validate Portal Accounts**: Allows users to mark the customer portal account emails as validated for the selected customers.
* **Inactive Users:** If enabled, it shows the list of users that are pending verification.


---

# 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://docs.xorosoft.com/xoroerp-1/admin/user/portal-user/portal-user-centre.md?ask=<question>&goal=<endgoal>
```

`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.