> For the complete documentation index, see [llms.txt](https://docs.dynalogic.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/security-roles.md).

# Security roles and privileges

Manage security roles, duties, and privileges to control access to Smart Connect features.

Smart Connect integrates with Dynamics 365 Finance & Operations security framework. Access to Smart Connect forms, data, and functions is controlled through security roles, duties, and privileges.

## Security model overview

The Smart Connect security model follows F\&O standards:

1. **Roles** – Collections of duties assigned to users
2. **Duties** – Collections of privileges for a functional area
3. **Privileges** – Permission to perform a specific action (read, create, update, delete)

A user has access to a Smart Connect feature only if they are assigned a role that includes the necessary privilege.

## Built-in Smart Connect roles

Navigate to **System administration > Security > Security roles** and filter for Smart Connect roles.

### SmartConnectAdmin

* **Purpose:** Full administration of Smart Connect
* **Privileges:** All Smart Connect features, all operations
* **Typical users:** IT administrators, Smart Connect implementation team
* **Includes duties:**
  * Connector management
  * Queue administration
  * Processor configuration
  * Parameter management
  * User and role management

### SmartConnectProcessingManager

* **Purpose:** Monitor and manage queues and process execution
* **Privileges:** View queues, retry failed messages, view logs, restart processors
* **Typical users:** Operations team, queue monitors
* **Does NOT include:** Connector or processor configuration, parameter changes

### SmartConnectAnalyst

* **Purpose:** Configure Smart Connect workflows and data mappings
* **Privileges:** Create/edit connectors, queues, processors, business processes, attributes
* **Typical users:** Business analysts, integration consultants
* **Does NOT include:** User management, parameter changes, system administration

### SmartConnectViewer

* **Purpose:** View-only access to Smart Connect
* **Privileges:** View queues, view logs, view processors
* **Typical users:** Read-only auditors, reporting users
* **Does NOT include:** Create or edit anything

## Core duties and privileges

### Connector management duties

| Duty                | Privilege                               | Action                          |
| ------------------- | --------------------------------------- | ------------------------------- |
| Maintain connectors | Create, read, update, delete connectors | Configure connectors            |
| Manage certificates | Upload, delete certificates             | Manage connector authentication |
| View connectors     | Read-only access                        | View connector list and details |

### Queue administration duties

| Duty                  | Privilege                           | Action                               |
| --------------------- | ----------------------------------- | ------------------------------------ |
| Maintain queues       | Create, read, update, delete queues | Configure queues                     |
| Monitor queues        | Read queue status and logs          | View queue health and message status |
| Retry failed messages | Update message status, reprocess    | Retry stuck or failed messages       |
| View queue logs       | Read queue response logs            | View message processing history      |

### Processor configuration duties

| Duty                | Privilege                               | Action                         |
| ------------------- | --------------------------------------- | ------------------------------ |
| Maintain processors | Create, read, update, delete processors | Configure data transformations |
| Define mappings     | Create field mappings                   | Map source to target fields    |
| Test processors     | Execute test runs                       | Validate processor logic       |
| View processor logs | Read processor execution logs           | Review processing history      |

### Business process duties

| Duty                              | Privilege                              | Action                    |
| --------------------------------- | -------------------------------------- | ------------------------- |
| Maintain business processes       | Create, read, update, delete processes | Define workflow rules     |
| Maintain business process filters | Create, read, update, delete filters   | Define routing conditions |
| Maintain business process events  | Create, read, update, delete events    | Define event handlers     |

### Reporting and analytics duties

| Duty           | Privilege                                 | Action                |
| -------------- | ----------------------------------------- | --------------------- |
| View reports   | Read Smart Connect reports and dashboards | Access analytics      |
| View telemetry | Read system performance data              | Monitor system health |

## DMS security roles (Document Management System)

If DMS is installed, additional roles control document processing:

### SmartConnectDMSManager

* **Purpose:** Manage DMS workflows and document processing
* **Includes:** All document processing configuration, format management, Document Warehouse integration
* **Typical users:** DMS implementation team, document process owners

### SmartConnectDMSOperator

* **Purpose:** Monitor and reprocess documents in DMS workflows
* **Includes:** Monitor document queues, reprocess failed documents
* **Typical users:** Document processing operations, DMS support team

## Creating a custom role

If the built-in roles don't fit your organization:

1. Go to **System administration > Security > Security roles**
2. Click **New**
3. Enter a role name (e.g., `SmartConnectQueueAnalyst`)
4. On the **Duties** tab, add the specific duties this role needs
5. Click **Save**
6. Assign users to the new role via **System administration > Security > Assign users to roles**

## Assigning roles to users

1. Go to **System administration > Security > Assign users to roles**
2. Select or search for the user
3. Check the roles to assign
4. Click **Save**

Changes take effect on the user's next login.

## Data-level security (table permissions)

Smart Connect respects F\&O data-level security:

* **Legal entity:** Users see only queues and data for their assigned legal entity
* **Department:** Some attributes and placeholders can be filtered by department
* **Custom dimensions:** Organizations can add custom data restrictions

Verify users have access to the required legal entities and dimensions.

## Delegation and temporary access

For temporary access or role delegation:

1. Go to **System administration > Security > Delegations**
2. Create a delegation rule specifying:
   * Which role is delegated
   * To which user (delegate)
   * Time period (start and end date)
   * Approval requirement (optional)
3. Save

The delegate has all privileges of the role for the specified period.

## Troubleshooting access issues

| Issue                                     | Cause                                    | Solution                                                      |
| ----------------------------------------- | ---------------------------------------- | ------------------------------------------------------------- |
| User cannot see Smart Connect menu        | Role doesn't include required duty       | Assign appropriate Smart Connect role                         |
| User can view queues but not edit         | Has Viewer role, needs Analyst role      | Assign SmartConnectAnalyst role                               |
| Document Warehouse features not available | DMS not installed or user lacks DMS role | Install DMS or assign SmartConnectDMSManager role             |
| "Access denied" when retrying message     | Doesn't have retry privilege             | Assign SmartConnectProcessingManager role or appropriate duty |

## Best practices

* **Principle of least privilege:** Assign the minimum role needed for the user's job
* **Regular access reviews:** Quarterly, review who has which roles and whether it's still appropriate
* **Separate by function:** Don't assign all roles to one person; separate admin, analyst, and operator roles
* **Document changes:** When modifying a custom role, note the reason in change history
* **Test in dev environment:** Test new role configurations before deploying to production

## Related pages

* [Parameters and settings](https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/parameters.md)
* [Connectors and connectivity](https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/connectors-and-connectivity.md)
* [Queues and message handling](https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/queues-and-message-handling.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.dynalogic.com/birds-smart-connect/setup-and-configuration/security-roles.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
