Accessing and Navigating¶
Communication Services Administration is accessed through the IFS Nexus platform using a tenant- and environment-specific URL. Authentication and tenant context determine what a signed-in user can see and do.
About Application Access¶
Users sign in with an authorized organizational account. After authentication, the platform establishes the tenant context and evaluates the user's permissions before displaying the application.
The application is tenant-aware: Contact Centers, Email Templates, Email Providers, Mailboxes, role assignments, and Email History all belong to the tenant currently being accessed.
Note: Always verify the tenant and environment before creating, changing, disabling, or deleting a configuration.
Prerequisites¶
Before accessing the application, confirm that:
- The user has a valid account in the organization's identity system.
- The user can sign in to the applicable IFS Nexus environment.
- The tenant has access to Communication Services.
- The user has the necessary platform permissions and a required Communication Services tenant role.
- The browser and network can reach the tenant URL, and the correct environment (development, test, staging, production) is being used.
Having access to open the application does not guarantee full access — a user may have read-only access, or lack permission for specific operations.
Opening the Application¶
The administration base path is:
/comms/admin
The full URL depends on the tenant's hostname:
https://<tenant-host>/comms/admin
Opening this URL should always land on the Dashboard — the application should not automatically redirect to Contact Centers or another configuration page.

Application shell showing the Dashboard
Application Access Flow¶
Users never connect directly to Communication Services backend components; requests are routed through the platform infrastructure:
- Platform ingress receives the request to the tenant-specific administration URL.
- Platform services route the request through the configured gateway.
- The platform authenticates the user and establishes the tenant context.
- Communication Services Administration loads and requests authorized information from Communication Services APIs.
- Results are displayed according to the user's permissions.

Application access flow
Authentication¶
Sign-in uses the IFS Nexus platform and the organization's configured identity provider — there is no separate username or password for Communication Services. Depending on the environment, this may include username/password, single sign-on, multi-factor authentication, conditional access, or session/device verification.
After authentication, the application obtains the signed-in user's context, including user identifier, display name, tenant identifier, tenant name, platform permissions, and Communication Services role assignments.
Tenant Context¶
A tenant is an isolated organizational context within the platform. When the application opens, it establishes the tenant tied to the requested hostname and authenticated session; this tenant context determines which data and configurations the user can access.
Language Selection and Localization¶
Depending on enabled languages, navigation labels, page titles, form labels, buttons, messages, and status labels are localized. The current specifications reference English and Swedish.
To change the language:
- Open the language selector in the application header.
- Select an available language.
- Wait for the application labels to update.
- Verify the selected page and any entered data before continuing.
Note: Changing the interface language does not translate user-entered content — resource names, email addresses, template content, or provider configuration remain as entered.