Skip to main content

Lesson 3 · Preparing the environment: modules, profiles and users

M
Written by Mairu

Path

Duration

Level

Before you start

🔵 Configurator · Level 1

35 min

Starter

Lessons 1 and 2 · User with access to Settings

A form needs a place to live (a module) and someone who can use it (a profile with permissions). If you prepare this first, everything else falls into place; if you leave it for the end, you'll end up with forms that nobody can see.

🎯 By the end you'll know

  • How to organize the menu with modules and submodules.

  • How to create the structure of departments and job positions.

  • How to design profiles and understand the permissions matrix.

  • How to create users and decide which screen they see when they log in.


🧠 The idea: who everyone is and what they can do

Mairu separates three things that are best kept apart:

Concept

Answers

Where it's configured

Department and job position

Which area do they belong to and what function do they perform?

Settings > Departments

Profile (role)

What can they see and do in Mairu?

Settings > Security

User

Who is this person?

Settings > Users

A user has a department, a job position and a profile. The department and job position are used to assign work (tasks, notifications); the profile is used to grant permissions.

💡 Design profiles by function, not by person: Operator, Quality, Supervisor, Administration. When someone new joins, you'll only have to assign them the right profile.

The four permissions

For each profile and each form (or an entire module) you enable:

Permission

What it allows

👁️ Read

See everyone's responses. Without it, the user only sees the ones they created themselves

➕ Create

Create new responses

✏️ Edit

Modify responses

🗑️ Delete

Delete responses


🛠️ Guided practice: the groundwork for the Packaging control

Step 1 · Create the module

In Settings > Modules create the Quality module and, inside it, the Packaging submodule. Choose an icon and a color: that way users will recognize it in the menu.

Step 2 · Create departments and job positions

In Settings > Departments create:

  • Production, with the job position Packaging operator.

  • Quality, with the job positions Quality technician and Quality manager.

Step 3 · Create the profiles

In Settings > Security click New profile and create:

  • Operator: will fill in the controls.

  • Quality: will review the controls and receive the alerts.

For now leave the Home path empty: you'll configure it in lesson 13, once you have the dashboards.

📌 There are no forms in Packaging yet, so you'll grant the permissions over the Packaging control in lesson 5. Take a look at the matrix now: rows = modules and forms, columns = profiles.

Step 4 · Create test users

In Settings > Users create two users:

User

Profile

Department / Job position

operario.prueba

Operator

Production / Packaging operator

calidad.prueba

Quality

Quality / Quality manager

Give calidad.prueba a real email address you have access to: you'll use it in lesson 9 to receive the alerts.

⚠️ The user code must be unique. Choose a convention (for example firstname.lastname) and stick to it; if you integrate Mairu with other systems, this code can be used as an identifier.


🔍 Check that it works

  • Log in as operario.prueba in another private window: they should get in without errors.

  • Their menu still has no Quality > Packaging form they can use. That's correct: the form and its permissions don't exist yet. You'll check it again in lesson 5.


⚠️ Common mistakes

  • Creating a profile per person. With 50 users you'll have 50 columns that are impossible to maintain.

  • **Granting only Create and being surprised that the operator can't see their colleagues' controls.** That's expected: without Read they only see their own. Decide consciously what each profile should see.

  • "I changed the permissions and it doesn't work." Check that you clicked Save in the Security matrix.

  • Configuring permissions one by one in large structures. Use the shortcuts: enabling a permission on the module row applies it to all its forms.


🏋️ Challenge

Add a Production supervisor profile that can see all the packaging controls, but can't create or delete them. Create a test user with that profile. What permissions will you give them once the form exists?


📚 Learn more

Did this answer your question?