How to Add a User in EDGEBIC

To add a user in EDGEBIC by User Solutions you open the Security tab, click New user, fill in the dialog, tick the role that person needs, and leave the must-change flag on so they choose their own password at first sign-in. The account is a sign-in identity; what the person can actually do comes from the role you attach, so the role tick is the part that matters most.

This is the single task of creating one account. For the wider picture of how users, roles, and permissions fit together, read users and roles explained, and for the full setup walkthrough see how to set up users and roles.

Before You Start

Three things make this go cleanly, and each prevents a specific dead end:

• You are signed in as an administrator, or as a user whose role includes the security permissions. The whole Security tab is hidden from anyone who lacks them.
• The role the new person needs already exists. If it does not, create it first with how to create a role, because a user with no role can sign in but can do nothing.
• You know the password policy. By default a password needs at least 8 characters with one uppercase letter, one lowercase letter, and one digit. Your installation may be stricter.

Adding the User

1. Open the Settings tab from the main navigation and click the 🔒 Security tab. Two sub-tabs appear: Users and Roles & Permissions.

2. On the Users sub-tab, click New user. The user dialog opens.

3. Fill in the fields:

   Field	Required	What it does
   Username	Yes	The sign-in name, 3 to 64 characters. Not case-sensitive at sign-in, so JSmith and jsmith are the same login.
   Full name	No	The display name shown in the identity strip on the toolbar.
   Email	No	Contact and reference only.
   Password	Yes	The initial password. It must meet the policy, and the hint under the field shows the rules.
   Active	No	Leave ticked. An unticked account cannot sign in.
   Must change password on next login	No	Leave ticked for new hires so the person sets a password only they know.
   Roles	No, but do it	Tick every role this person holds. Rights are the union of all ticked roles.

4. Tick the correct role in the Roles group. For a production planner that is usually a single Planner role; tick a second role only if the person genuinely does two jobs.

5. Click the save button. The new user appears in the Users grid with columns for Username, Full name, Email, Roles, Active, Locked, and Last login.

The other toolbar buttons on the Users tab handle everything after creation: Edit to change details or roles, Reset password, Unlock, Activate / Deactivate to bar sign-in without deleting, and Delete.

What Changes When You Save

Saving writes one account and, through the role tick, the exact set of things that person can see and click.

A username is not case-sensitive at sign-in but is stored as you typed it, so pick a house convention (first initial plus surname is common) and stick to it.

How to Check It Worked

Look at the Users grid: the new row should show the right roles in the Roles column and a ticked Active state. Then have the person sign in from their own machine. If must-change is on, they should hit the change-password prompt on the first attempt, set their own password, and land on the main window with exactly the tabs their role allows. If a tab or button they need is missing, the role is short a permission, not the account: fix it on Roles & Permissions.

Common Mistakes

Saving with no role ticked. This is the top cause of "the new user can log in but can't do anything." Rights come only from roles, so an account with none is inert. Always tick at least one role, and confirm it on the grid afterward.

Sharing one login across a team. The audit trail only maps actions to people if each person has their own account. Never create a single shared "planner" login; create one account per person. This and related pitfalls are collected in user and permission mistakes.

Deleting instead of deactivating when someone leaves. Use Activate / Deactivate for departures so the account history stays intact and the username cannot be reused by accident. Delete only when you are certain the identity should be gone for good.

Expecting a self-service password link. New users do not receive a reset email unless your installation has that turned on. The reliable path is admin-set with the must-change tick, covered in how to reset a user's password.

A Quick Worked Example

Acme Industries grows from one planner to a small team. The founding administrator already exists from first launch. To add a planner named Jane Smith, the admin opens Settings → 🔒 Security → Users, clicks New user, and fills in Username jsmith, Full name Jane Smith, and an initial password that meets the policy. Must change password on next login stays ticked, and the Planner role is ticked in the Roles group. Save, and jsmith appears in the grid.

Jane signs in from her own PC with the temporary password, is immediately prompted to set a new one, and lands on the main window with the Production and Master Data tabs her Planner role allows, but no Security tab. A supervisor named mlopez is added the same way with the Supervisor role instead. Each person has one account, so when the audit trail records a schedule generated or an actual logged, it maps to a real name. That is the whole reason shared logins are a mistake: they turn every action into "someone."

Next Steps

If the role you needed did not exist yet, how to create a role is the companion task, and it is where you decide precisely what the account can do. For the full task library, see the EDGEBIC how-to hub, and for where security sits in the wider platform, EDGEBIC.