Cloud Replicator Documentation
Index

Permissions

This guide explains the permissions required to configure and use Cloud Replicator in Business Central.

Permission Overview

Cloud Replicator requires different levels of access depending on the user's role:

Role Required Access
Administrator Full configuration and execution access
Operator Run replications and view logs
Viewer View configuration and logs only

Required Permissions

Configuration Tables

Users who configure Cloud Replicator need access to these tables:

Table Table ID Access Level
Cloud Replicator Setup EFQ 70319890 Read, Insert, Modify, Delete
Replicator Table Mapping EFQ 70319891 Read, Insert, Modify, Delete
Field Mapping EFQ 70319892 Read, Insert, Modify, Delete
Replication Log EFQ 70319893 Read, Insert, Modify, Delete
Engine Pulse EFQ 70319885 Read, Insert, Modify, Delete
Replication Parameters 2 EFQ 70319886 Read, Insert, Modify, Delete

Codeunit Execution

Users who run replications need execute permission on:

Codeunit Codeunit ID Purpose
Cloud Replicator Engine EFQ 70319891 Main replication engine
Cloud Replicator JQ Runner EFQ 70319900 Job Queue entry point (scheduled runs)
Replication Runner EFQ 70319896 Background job execution
Replicate One Table EFQ 70319895 Single table replication

Data Access

To replicate data, users need read access to all Business Central tables being replicated. For example:

  • Customer table (Table 18)
  • Sales Header table (Table 36)
  • Item table (Table 27)
  • Any custom tables you want to replicate

Setting Up Permissions

Using SUPER Role

The simplest approach is to assign the SUPER user role to users who manage Cloud Replicator. This provides full access to all required tables and codeunits.

When to use: Small organizations or when dedicated Cloud Replicator administrators already have SUPER access.

Creating a Custom Permission Set

For organizations that follow the principle of least privilege, create a custom permission set:

Step 1: Create the Permission Set

  1. Search for "Permission Sets" in Business Central
  2. Click "New" to create a new permission set
  3. Enter a code (e.g., "CLOUD-REPLICATOR") and name

Step 2: Add Table Permissions

Add the following table permissions:

Table 70319885 "Engine Pulse EFQ" = RIMD
Table 70319886 "Replication Parameters 2 EFQ" = RIMD
Table 70319890 "Cloud Replicator Setup EFQ" = RIMD
Table 70319891 "Replicator Table Mapping EFQ" = RIMD
Table 70319892 "Field Mapping EFQ" = RIMD
Table 70319893 "Replication Log EFQ" = RIMD

Where R = Read, I = Insert, M = Modify, D = Delete

Step 3: Add Codeunit Permissions

Add execute permission for:

Codeunit 70319885 "Azure Table V2 EFQ" = X
Codeunit 70319886 "Cosmos DB Core V2 EFQ" = X
Codeunit 70319887 "Cosmos DB Table V2 EFQ" = X
Codeunit 70319891 "Cloud Replicator Engine EFQ" = X
Codeunit 70319894 "Json Tools EFQ" = X
Codeunit 70319895 "Replicate One Table EFQ" = X
Codeunit 70319896 "Replication Runner EFQ" = X
Codeunit 70319898 "Azure AI Search EFQ" = X
Codeunit 70319899 "Engine Pulse Update EFQ" = X
Codeunit 70319900 "Cloud Replicator JQ Runner EFQ" = X

Step 4: Add Data Table Permissions

Add read permission for all tables you want to replicate. For example:

Table 18 "Customer" = R
Table 27 "Item" = R
Table 36 "Sales Header" = R
Table 37 "Sales Line" = R

Step 5: Assign to Users

  1. Search for "User Permission Sets" or access through User Card
  2. Add your custom permission set to the appropriate users

Job Queue Permissions

If using scheduled replication, the user account running Job Queue entries needs:

  • All Cloud Replicator permissions listed above
  • Job Queue administration permissions
  • Session management permissions (for background sessions)
  1. Create a dedicated service account for Job Queue
  2. Assign SUPER role or comprehensive custom permission set
  3. Configure Job Queue entries to run under this account

Permission Troubleshooting

"You do not have permission" Errors

If users receive permission errors:

  1. Verify the user has the Cloud Replicator permission set assigned
  2. Check if the specific table or codeunit is included in their permissions
  3. Ensure read access exists for tables being replicated

Job Queue Failures

If scheduled replications fail with permission errors:

  1. Check the Job Queue entry's "User ID" setting
  2. Verify that user has all required permissions
  3. Review the Job Queue Log for specific error messages

If users cannot find Cloud Replicator pages:

  1. Verify the extension is installed
  2. Check page permissions in the user's permission set
  3. Users need at least indirect access through codeunits that use the pages

Security Best Practices

Principle of Least Privilege

Assign only the permissions users need for their specific roles. Not all users need full configuration access.

Service Accounts for Automation

Use dedicated service accounts for Job Queue and automated processes. This provides:

  • Clear audit trail
  • Easier permission management
  • Isolation from interactive user accounts

Regular Permission Reviews

Periodically review who has access to Cloud Replicator and ensure permissions align with current job responsibilities.

Credential Security

Only administrators should have access to the Cloud Replicator Setup page where Azure credentials are stored. Consider restricting access to this page through page-level permissions.