> For the complete documentation index, see [llms.txt](https://docs.guardware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.guardware.com/documentation/partner-portal/partner-portal-detailed-guides/logging-in.md).
# LOGGING IN
Before accessing the Partner Portal, ensure that a partner account has been provisioned by GuardWare. The Partner Portal supports sign-in using email credentials, Microsoft 365, or Google Workspace.
The Partner Portal supports two roles:
* **Partner Admin:** Has full access to Partner Portal functions, including managing other Partner Portal users and reactivating deactivated organisations.
* **Partner User:** Can perform customer management functions but cannot add or modify other Partner Portal users or reactivate deactivated organisations.
## Sign in via Email
Email sign-in uses credentials provided by GuardWare. During the first login, you must configure two-factor authentication (2FA) and change the temporary password provided in your welcome email.
1. Enter your email and the one-time password from your welcome email, and click **Log In**.
2. Set up 2FA using an authenticator app, such as Microsoft Authenticator or Google Authenticator.
3. Enter the authentication code generated by your authenticator app.
4. Change your password when prompted, then sign in again using your new password.
5. Enter the authentication code from your authenticator app.
6. Accept the **End User Licence Agreement (EULA)**. The EULA is displayed only once.
After the initial setup, 2FA only needs to be completed as part of the normal email sign-in process. It does not need to be configured again unless it is reset from the Management Console.
## Sign in via Microsoft Account
Microsoft 365 sign-in uses your organisation's Microsoft Entra ID authentication.
1. Ensure your Microsoft 365 account is associated with your organisation's Microsoft Entra ID environment.
2. Click :microsoft: **Microsoft** to continue with Microsoft authentication.
3. Authenticate using your Microsoft 365 account.
4. Accept the **End User Licence Agreement (EULA)**. The EULA is displayed only once.
The Partner Portal does not require separate 2FA configuration for Microsoft 365 sign-in. Any authentication or multi-factor authentication requirements configured for your Microsoft account are handled by Microsoft.
## Sign in via Google Workspace Account
Google Workspace sign-in uses your organisation's Google authentication.
1. Ensure your account belongs to a Google Workspace organisation.
2. Click :google: to continue with Google authentication.
3. When prompted, click **Continue** to grant the required permissions.
4. Accept the **End User Licence Agreement (EULA)**. The EULA is displayed only once.
The Partner Portal does not require separate 2FA configuration for Google Workspace sign-in. Any authentication or multi-factor authentication requirements configured for your Google account are handled by Google.
For a walkthrough of the core tasks, refer to the [**Partner Portal Quick Start Guide**](/documentation/partner-portal/getting-started/partner-portal-quick-start-guide.md).
---
# 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.guardware.com/documentation/partner-portal/partner-portal-detailed-guides/logging-in.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.
