Administration

The Admin group in the menu holds the pages for running your organisation’s Lintel: who has access, how they sign in, what the product looks like and which add-on modules run. Most pages are for the tenant admin role. A few, marked below, are for the product owner, who looks after the platform as a whole. A tenant admin does not automatically see content such as the capability model; give them a content role as well if they need one.

Audit log

A record of who did what and when, newest first, with times in UK time. Use it to answer “who changed this?” or to check that sensitive actions, such as a self-approval or a module version being committed, were recorded.

• When, Who, Action, Item, Detail are shown for each entry; the detail shows the values before and after.
• Use Newer and Older to page through.
• “Not signed in” means the action happened before anyone signed in, such as a sign-in attempt.

The log cannot be edited. It is available to tenant admins.

Sign-in security

Settings for how people prove who they are. A tenant admin sees the organisation’s passkey rule and a list of people with their passkey counts. The product owner has a separate page, Sign-in security (all tenants), which overrides every organisation.

Read the two cards in turn: first whether a passkey is required as a second step, then the passkeys held by each person. Changes apply from the person’s next sign-in.

Passkey as a second step

A passkey second step asks for a passkey after a password or emailed link. Signing in with a passkey alone already counts as two factors, so it is never asked twice.

For a tenant admin:

1. Tick Require a passkey second step for everyone here.
2. Press Save.

People who have no passkey yet are let in and asked to add one, so nobody is locked out. If the product owner has set the rule for everyone, the card tells you and you cannot change it.

For the product owner, the platform page offers three choices: let each organisation decide, require it everywhere, or switch it off everywhere. What is set there overrides every tenant admin.

Passkeys by person

Lists every person with how many passkeys they have. Use Reset passkeys when someone has lost a phone or device.

1. Find the person and press Reset passkeys.
2. Their passkeys are all removed and they are signed out everywhere.
3. Send them a sign-in link (see Users and roles) so they can sign in and add a new passkey.

The button only appears for people who have at least one passkey. The reset is recorded in the audit log.

Users & roles

The page for deciding who can use Lintel and what they can do. It lists people with their roles, whether they are active, and when they last signed in. Roles available are Viewer, Contributor, Architect, Capability model owner, Governance owner, ARB secretary, ARB member and Tenant admin.

• A person can hold several roles; some imply others (an Architect can also contribute and view).
• Use Manage on a row to change roles, send a sign-in link, disable or enable the person, or delete them.
• Deleting removes their roles and sign-ins for good; the audit log keeps what they did.

Disable rather than delete when someone leaves, so history stays easy to read.

People with access

The table of everyone with an account. Open Manage beside a person to act on them.

1. Tick or untick roles and press Save roles.
2. Send sign-in link emails them a fresh link, useful after a passkey reset.
3. Disable user stops them signing in without removing anything; Enable user brings them back.
4. To delete, tick the confirmation box, then Delete user.

You cannot delete yourself. The status chip shows Active or Disabled.

Add a person

Add someone and give them roles in one step.

1. Enter their email address and, if you like, their name.
2. Tick the roles. Each has a short description beside it; Viewer is ticked by default.
3. Press Add and send link.

They are emailed a link to sign in, where they can add a passkey or set a password. They only see what their roles allow. Give people the smallest set of roles they need.

Approving change sets

Changes to the repository normally go through a change set, which must be approved by an architect other than its author. This card handles the case of an organisation with only one architect.

• Tick Let the only architect approve their own change sets and Save to allow it.
• Each self-approval is recorded in the audit log.
• Untick it as soon as a second architect joins.

See Change sets for how approval works.

Set up product ownership

This card appears only on a test site where no product owner exists yet. Until there is one, nobody can make module versions available.

1. Press Make me the product owner.
2. The role is granted to your email address and recorded in the audit log.

On a live site product owners are set up by the platform operator, not here. See Product owners.

Modules and licences

Modules are add-on features released separately from the core, such as RAID, Reports or the ArchiMate modeller. This page lists each one with its licence type, version, status and whether it is running.

• Core modules are included with every licence. Add-ons are licensed for the whole organisation or per named user.
• Open a row, choose a version to run for this environment and press Use this version.
• Switch on or Switch off controls whether it is running. Your data stays whichever you choose.
• To add a licence, open Enter a licence key, paste the key you were sent and press Add licence key.

Status words such as “Licence needed” or “Licence expired” tell you what to fix. A per-user module also needs people assigned to seats; see Seats.

Live only runs versions that have been tried in staging. The “versions tried here” and “versions approved in staging” boxes at the bottom carry that list from one to the other when the two sites are on different servers. Pasting adds to the list and never removes a version.

Seats

For a module licensed per named user, this shows how many seats are in use out of those licensed, and who holds them.

1. Type the person’s email in Give a seat to (suggestions come from your users) and press Assign seat.
2. Use Remove beside a person to free their seat.
3. Or press Give everyone access to let the whole organisation use the module; Back to named seats reverses that.

If more people are listed than seats licensed, those over the limit show “Over the limit: no access” until seats are freed or the licence is increased.

Product owners

For the platform’s product owners only. A product owner decides which module versions client organisations can choose, and holds the role by email address across the whole platform, separate from organisation roles.

• To add one, type an email address and press Add.
• To take the role away, press Remove beside their address.

Keep this list short and make sure at least one trusted person always holds it.

Module releases

For product owners. Lists every module version installed on this server, with the core version it needs, its data version and the oldest data it works with.

• Make available lets client admins choose that version.
• Withdraw stops new selections. Organisations already running it are not switched off.
• The status column shows who last changed it and when.

Making a version available is a deliberate step: install and test it first, then release it. Organisations still choose and switch it on themselves under Modules and licences.

Theme & branding

Lets a tenant admin make Lintel look like your organisation. Changes apply for everyone in your organisation straight away. Use the Preview at the bottom to see the effect before you are happy.

There are three cards: your logo, the colours and fonts, and a live preview. Reset to the Lintel default puts everything back.

Client logo

Your organisation’s logo appears in the top bar to the right of the signed-in person’s name.

1. Choose a PNG, JPEG or SVG file up to 512 KB. A wide logo about 160 by 40 pixels works best.
2. Press Upload logo.
3. Use Remove logo to take it off again.

Until a logo is uploaded, a placeholder shows. Tenant admins can click the placeholder to come straight here.

Look and feel

Choose the colours and type of the application.

• Menu bar colour, accent colour (buttons and the current page) and page background.
• Corner rounding from 0 to 16 pixels.
• Body font and heading font: a clean sans-serif or a serif.

Text colours on the menu bar and buttons are chosen automatically so they stay readable. Press Save theme to apply, or Reset to the Lintel default to undo.

Preview

A small sample of the top bar and a button using your current colours and logo, so you can judge a change.

It shows the saved theme, so save first, then check the preview. If the text is hard to read on your chosen colour, pick a different one.

Help guide links

Every page title and section heading in Lintel shows a small ? link. It opens the matching page of this academy in a new tab, straight to that section. Product owners control where those links point from Help guide links in the Admin menu.

Academy address

This is the web address the ? links start from, for example https://lintel-ea.com/academy/. Each link adds the area and the section to it.

1. Open Help guide links (product owners only).
2. Enter a full https address that ends with a slash, or leave it empty to hide the links everywhere.
3. Save. The change applies to every page at once and is recorded in the audit log.