Product: Mingcedar CONTROL

Users, roles, modules and branding | Mingcedar

Location: Admin → Access Control → Users. Viewing requires auth:view; editing requires auth:manage.

Published 2026-10-25T12:48:42.640328876Z Updated 2026-10-25T12:48:42.640328134Z

<div class="manual-doc-article manual-doc-article-section"><h2 id="security-modules">User guide: Users, roles, modules and branding</h2>

Manage accounts, permissions, services and branding. Configure menu access, runtime writes and API authorization separately.

<h3 id="security-modules-item-1">Access Control: manage users</h3>

<p>Location: Admin → Access Control → Users. Viewing requires auth:view; editing requires auth:manage.</p>

<ol>

<li>Create a user with username, display name, initial password, language and status.</li>

<li>Assign roles and, when appropriate, require a password change at the next sign-in.</li>

<li>Edit roles and state; a blank password preserves the existing one. After saving, check page and action access with that account.</li>

<li>Disable an account to stop further access. Review the account and confirmation prompt before deleting it.</li>

</ol>

</article>

<h3 id="security-modules-item-2">Access Control: roles and permissions</h3>

<p>Roles grant selected permissions regardless of their names.</p>

<ol>

<li>Open Roles and create a role with code, name, description and enabled state.</li>

<li>Find permissions by group, read their descriptions, select the required items and save.</li>

<li>Assign the role in Users. Verify viewing, editing, writes, alarm acknowledgement and exports separately.</li>

<li>Built-in roles cannot be deleted; the super-admin role remains enabled. If an entry is missing, check user status, enabled roles and the required permission.</li>

</ol>

</article>

<h3 id="security-modules-item-3">Runtime menus and sign-in requirements</h3>

<p>A menu’s login requirement controls access to that page. RUNTIME_PUBLIC_READ controls the deployment’s runtime read policy.</p>

<ol>

<li>Select the menu in Menus, set Login required, and save. The runtime entry uses its saved name, order and target page.</li>

<li>When public reads are enabled, runtime values, alarms and trends can be read within their scope. Disabling public reads requires a valid login.</li>

<li>Writes still check the user’s write permissions, the Tag’s runtime-write setting and the page’s declared capabilities.</li>

<li>IO State API Profiles and Access Keys are managed independently of menu login requirements.</li>

</ol>

</article>

<h3 id="security-modules-item-4">Modules: status and runtime control</h3>

<p>Location: Admin → Modules. Viewing requires site:view; management requires site:manage.</p>

<ol>

<li>Search by name, code or description, or filter by running, attention, disabled or offline state.</li>

<li>Select a module and inspect its status and available controls. Start, stop or restart only where those controls are available.</li>

<li>Stopping or restarting IO, Alarm, Trend or Script pauses intake and drains tasks. Review the impact, submit, then check the receipt, health and readiness. For unknown results, use Verify Original Request instead of resubmitting. View services without controls in System Status.</li>

<li>Use Devices for PLC connection and collection details. A running module does not prove a PLC is connected.</li>

</ol>

</article>

<h3 id="security-modules-item-5">Branding: title and logos</h3>

<p>Location: Admin → Branding. Requires branding:manage.</p>

<ol>

<li>Set the runtime title and upload the left and right logos. PNG, JPG and WebP are supported, up to 2 MB per file.</li>

<li>Check image proportions and text in the preview. Clearing a logo or restoring defaults changes the form first.</li>

<li>Save to apply, then open the runtime page to inspect the title and logos.</li>

</ol>

</article>

</div>

<strong>Figure 1: Access Control</strong>

<p>The role editor contains role details, built-in permissions and explanations of each permission. Review the intended grants before saving.</p>

</figcaption>

</figure>

<strong>Figure 2: Branding</strong>

<p>Branding shows the runtime title, left and right logo selectors, and the header preview.</p>

</figcaption>

</figure>

<strong>Figure 3: Modules</strong>

<p>The module list shows service status; the selected module shows local execution, access, and enabled status.</p>

</figcaption>

</figure>

</div>