First configuration: sign-in to runtime | Mingcedar

<div class="manual-doc-article manual-doc-article-section"><h2 id="foundation">User guide: First configuration: sign-in to runtime</h2>

Configure services, data, screens and access in order.

<div class="doc-card-list doc-tutorial">

<article class="doc-card">

<h3 id="foundation-item-1">1. Confirm endpoints and services</h3>

<p>Use the Portal endpoint reported by the installation.</p>

<ol>

<li>Sign in with a management account and open Admin → System Status.</li>

<li>Inspect site, version, the five runtime services, database and Redis; check the License page.</li>

<li>Choose the interface language from the header. Use Access Control to maintain users and roles.</li>

</ol>

</article>

<article class="doc-card">

<h3 id="foundation-item-2">2. Create Devices and Tags</h3>

<p>Location: Admin → Devices, Tags and Tag Diagnostics.</p>

<ol>

<li>Confirm the local site, create a protocol-specific Device and save. Inspect configuration application and connection state.</li>

<li>Add Tags with codes, addresses and types. The full Tag code combines its Device code and Tag code.</li>

<li>Add the target in Tag Diagnostics and confirm value, quality and timestamp before configuring alarms, trends, calculations or scripts.</li>

</ol>

</article>

<article class="doc-card">

<h3 id="foundation-item-3">3. Publish screens and configure access</h3>

<p>Location: Screen Files, Menus and Access Control.</p>

<ol>

<li>Upload and publish the complete screen directory, retaining relative asset paths.</li>

<li>Create a menu targeting the published screen, set its name, ordering and login requirement, and configure popups as needed.</li>

<li>Open the screen through the runtime menu and verify display, live values, alarms, trends and permitted actions with an operator account.</li>

<li>If remote capabilities are needed, connect sites and select the scope in Sites.</li>

</ol>

</article>

</div>

</div>