Accessing your platform environment

Once your GLBNXT Platform environment has been provisioned, your team can access it immediately through the platform console. This section covers how to log in, how to navigate the environment, and what you can expect to find when you first arrive.

Logging In

GLBNXT Platform is accessed via the platform console at platform.glbnxt.com. Depending on the configuration agreed during onboarding, you will log in using one of the following methods:

• SSO via your identity provider: if your organisation uses Azure AD, Okta, or Google Workspace, login is handled through your existing identity provider. Your credentials are the same ones you use across your organisation's other tools and services.

• Direct login: if SSO has not been configured for your environment, you will log in using the credentials provided to you during onboarding. It is recommended to update your password on first login and to enable multi-factor authentication immediately.

If you are unable to log in or have not received your credentials, contact your GLBNXT onboarding contact or reach out via the support channels described in the Support and Escalation section.

Navigating the Console

The platform console is your central access point for all services, tools, and administrative functions available in your environment. When you log in for the first time, you will see an overview of the components and services that have been deployed for your organisation.

The console is organised around the following areas:

• Applications: the AI tools, interfaces, and services deployed within your environment, including chat frontends, workflow builders, and any pre-configured solutions

• Model Hub: the models available for inference in your environment, including open-source models and any custom or fine-tuned models deployed for your organisation

• Data Services: your vector databases, object storage, and relational database instances

• Monitoring and Observability: dashboards and logs covering platform health, model usage, and audit activity

• Settings and Administration: user management, access controls, identity provider configuration, and environment-level settings

Not all areas of the console are visible to every user. What you see depends on the role assigned to your account. Administrators have full visibility across all areas, while developers and standard users see the components relevant to their work.

User Roles and Permissions

GLBNXT Platform uses role-based access control to manage what each user can see and do within the environment. Roles are assigned during onboarding based on the access list provided by your organisation.

Common roles include:

• Administrator: full access to all platform components, user management, and environment configuration

• Developer: access to applications, model endpoints, data services, and development tools, without administrative controls

• Viewer: read-only access to selected components and dashboards, suited for stakeholders who need visibility without making changes

Role assignments can be updated at any time by your platform administrator. For guidance on managing users and permissions, see the Team and User Management section.

Multi-Factor Authentication

Multi-factor authentication is strongly recommended for all platform users and is enforced by default for administrator accounts. If your organisation uses SSO, MFA is handled by your identity provider. If you are using direct login, MFA can be enabled within your account settings in the platform console.

First Steps After Logging In

Once you have logged in and confirmed your access, the recommended first steps are:

1. Review the applications and services available in your environment and confirm they match your onboarding summary

2. Check that all team members who require access have been provisioned with the correct roles

3. Connect to a model endpoint and run a test inference request to confirm your environment is operational

4. Review your observability dashboard to confirm that logging and monitoring are active

If anything in your environment does not match what was agreed during onboarding, contact your GLBNXT onboarding contact before proceeding with any development work.