Communication Services Administration¶
Communication Services Administration is the application for configuring, managing, and monitoring the email communication capabilities of IFS Nexus Communication Services.
About Communication Services Administration¶
The application centralizes the main email communication configurations. Authorized administrators can use it to:
- Organize communication resources using Contact Centers
- Create and manage reusable Email Templates
- Configure external Email Providers
- Create and maintain sender Mailboxes
- Assign tenant-level administration roles
- Control access to communication resources
- Monitor outbound email processing through Email History
- Investigate configuration and delivery-related problems
The application is tenant-aware: users see only the resources belonging to the tenant they are accessing, and only the features their permissions and role assignments allow.
Note: Communication Services Administration is for configuration, governance, and operational monitoring — it is not an email inbox and does not replace an external email service such as Microsoft 365.
Intended Audience¶
This guide is for users who configure, administer, support, or monitor Communication Services. Typical user types:
User types
| Type | Responsibilities |
|---|---|
| Communication Services administrators | Configure Contact Centers, Email Templates, Email Providers, and Mailboxes; may monitor outbound email activity and maintain resource-level access assignments. |
| Tenant administrators | Manage tenant-level access, assigning users, groups, or service accounts to Communication Services tenant roles. Tenant administration permission does not automatically grant access to operational resources — that is evaluated separately. |
| PII Officers | Handle personally identifiable information, privacy, data governance, and compliance responsibilities. Exact available features depend on permissions and other role assignments. |
| Support and implementation teams | Verify configuration, review email-processing information, investigate delivery failures, and gather troubleshooting information. |
Administration Capabilities¶
Dashboard
The application's home page; entry point to available administration features.
Contact Centers
Organize resources by business area, department, service, or operational responsibility (e.g. Customer Support, Finance Notifications). Email Templates and Email Providers associate with a Contact Center, which also identifies who owns, manages, sends from, or views its resources.
Tenant Roles
Control tenant-level responsibilities. Supported roles: Comms Admin, PII Officer. Roles can apply to users, groups, and service accounts, depending on the implemented tenant-role contract.
Email Templates
Reusable email content associated with a Contact Center, including name, authored language, subject, content, and content type.
Email Providers
Define how Communication Services connects to an external email delivery service: name, Contact Center, provider type, connection configuration, authentication/credential references, status, and ownership.
Mailboxes
Sender identities used through an Email Provider: email address, display name, associated provider, status, and owner/sender/viewer assignments.
Email History
Operational visibility into outbound messages — processing status and metadata. Monitoring only; not used to create, edit, delete, or resend messages.
How the Components Work Together¶
Component relationships
| Component | Purpose | Relationship |
|---|---|---|
| Contact Center | Organizes resources and access | Owns/governs templates and providers |
| Email Template | Defines reusable message content | Associated with a Contact Center |
| Email Provider | Connects to an external delivery service | Associated with a Contact Center |
| Mailbox | Defines the sender identity | Associated with an Email Provider |
| Communication Services | Processes the outbound message | Uses the configured resources |
| Email History | Monitors processing and delivery | Displays the result of outbound processing |
Typical configuration and delivery flow:
- An administrator creates a Contact Center for a business function.
- An Email Provider is created for that Contact Center.
- A Mailbox is created and connected to the Email Provider.
- An Email Template is created for reusable message content.
- A business application or process submits an email request.
- Communication Services processes the request using the applicable configuration.
- The message and its processing status become available in Email History.
Example configuration
Contact Center: Customer Support • Email Provider: Customer Support Microsoft 365 Provider • Mailbox: support@example.com • Email Template: Case Received Confirmation
When a customer submits a support case, the application requests an email using the configured template and mailbox. Communication Services processes it through the Email Provider, and an administrator can review the message status in Email History.
Configuration and Monitoring Responsibilities¶
Configuration features define how resources are organized and used — Contact Centers, Tenant Roles, Email Templates, Email Providers, Mailboxes, and resource access assignments. Changes can affect future processing, so review dependencies before editing, disabling, or deleting a resource.
Monitoring features (Email History) show information about communication already submitted for processing — whether an email is waiting to be processed, being processed, successfully processed, delivered, retrying after an error, failed, or canceled.
Tenant-Aware Operation¶
Each administration session is established within a particular tenant context. At startup, the application obtains the tenant identifier and name, the signed-in user's identifier and name, available permissions, and tenant-role assignments. This information is used to display the correct tenant context, retrieve that tenant's resources, determine accessible pages and read-only/update access, control available operations, and prevent access to another tenant's data.

Simplified application start-up process flow
Security and Authorization¶
A layered authorization model applies:
- The platform authenticates the user.
- The application establishes the tenant context.
- Platform permissions are loaded.
- Communication Services tenant-role assignments are retrieved.
- Resource-level access assignments are evaluated where applicable.
- The application enables, disables, or hides features and operations according to the result.
A user may experience one of three access levels:
Access levels
| Level | Description |
|---|---|
| Full administration access | Can view and perform the permitted configuration or monitoring operations. |
| Read-only access | Can view information but cannot create, edit, delete, enable, disable, cancel, or update the resource. |
| Restricted access | Cannot open the page or view the protected information. |
Note: Being able to open a page does not mean a user can perform every action on it.
Resource Ownership and Access¶
Contact Centers, Email Providers, and Mailboxes can hold access assignments identifying who is responsible and what they can do. Categories vary by resource but may include Owner, Supervisor, Sender, and Viewer. Users and groups are retrieved from the organization's directory.
Recommended practices:
- Assign only the access required for a user's role; use groups for shared responsibilities.
- Avoid unnecessary individual assignments; review assignments when users change teams or responsibilities.
- Remove inactive users and obsolete groups; maintain at least one responsible owner where ownership is required.