Settings
Settings and user management
The Settings workspace is where your organization is configured: its connected M3 environments, its members, their roles and which features they can use, and a few personal settings.
Open it from Settings in the sidebar. Most of the page is visible to every user, but only administrators can change it. Users with the Viewer role don't see Settings at all.
General
- Loupe organization name is your organization's identifier in Loupe.
- Organization logo is shown in the sidebar and in the organization switcher. Administrators can Upload logo, Replace logo or Remove it. Images can be PNG, JPEG, GIF, WebP or SVG, up to 1 MB, and are cropped to a square.
Tenants
This section lists the M3 environments connected to your organization, with their URL and when they were added. Environments can be added and removed, but not edited.
- Add New Environment connects a new M3 environment from an
.ionapifile. See Set up your organization for the full walkthrough, including how to create the Authorized App in Infor OS. - Defaults marks one environment as Left and one as Right. These are preselected in Compare for everyone in the organization.
- Drag the handle to change the order in which environments appear throughout Loupe.
- Details for authorized app shows the exact values to paste into Infor OS when creating the Authorized App. Click a value to copy it.
Saved passwords
If you work with on-premise M3 environments that show their own login form, Loupe can remember the username and password for you. They are stored encrypted on this computer only and never synced anywhere. Use Show to reveal a saved password and Delete to forget it.
User management
Administrators manage who belongs to the organization and what they can do.
Add Members by typing a colleague's email address and clicking Add. If they've signed in to Loupe before, they become a member immediately. Otherwise they are listed with an Invited badge and receive an email with a download link. The invite turns into a membership the first time they sign in.
Each member row shows:
- One checkbox per M3 environment. A member only sees the environments that are ticked here. Remember this step after adding someone, or they will have nothing to sign in to.
- One checkbox per feature: Explore, Compare, Automate, Run and, if your organization has it, Code. A member only sees the features that are ticked. See Features.
- A role dropdown: User, Viewer or Admin.
- Remove, which removes the member or cancels the invite.
You can't change your own role or remove yourself. Reload users refreshes the list.
Roles
| Role | What they can do |
|---|---|
| Admin | Everything. Connect and remove environments, set defaults, upload the logo, add and remove members, change roles, environment access and feature access, and manage per-user sharing. |
| User | The default. Create, save and share compares, API collections and automations. Sees Settings, but not User management. |
| Viewer | Read-only. Sees only items shared with the whole organization, can open and run them, but cannot create, edit or copy anything. Settings is hidden. |
Features
Roles decide what a member may do. Features decide which parts of Loupe they see at all. Each member row has one checkbox per feature, and a feature that is not ticked disappears from that member's sidebar.
| Feature | What it opens |
|---|---|
| Explore | Explore M3 data |
| Compare | Compare environments |
| Automate | Build automations |
| Run | Run APIs |
| Code | Loupe Code. Only shown when your organization has Code enabled. |
How it works:
- New members and invites start with Explore, Compare, Automate and Run ticked. Code is never on by default; an administrator grants it per member.
- Only administrators can change feature access. Unlike roles, you can change your own features, since that can never lock you out of the organization.
- Feature access set on an invite is carried over to the membership the first time the person signs in.
- A change shows up the next time the member reloads Loupe or switches organization; the tab is then gone from their sidebar. When someone switches to an organization where they lack the feature they were using, Loupe opens the first feature they do have there.
- Roles still apply inside each feature. A Viewer with Compare ticked can open and run shared compares, but still cannot create their own.
- Unticking every feature does not hide everything. A member with no features ticked still sees the four classic features, so use roles, not features, to restrict what someone may do.
Loupe Code is enabled per organization
Loupe Code is part of a separate subscription, so the Code checkbox only appears once it has been enabled for your organization. After that, administrators grant it to individual members like any other feature. Contact the Loupe team if you would like to add Code to your subscription.
Switching organizations
If you belong to more than one Loupe organization, the grid icon at the top left opens the organization switcher. Click an organization to switch to it. Drag to reorder the list; the order is personal to you. Loupe warns you if you have unsaved work.
About Loupe
The About Loupe button at the bottom of Settings shows the version of the app and of the desktop shell. Include both when you contact support.