What's new

Release notes for the core platform and the modules, newest first.

Core

Core 12.8.7

Your IP rules now apply to the web sign-up form and to the web API's sign-in and sign-up.

Security

  • Your IP rules now apply when someone signs up on the sign-up form, with Allow public registration on, as they already did to signing in. Before, someone on a network address your rules refuse could create an account there and be signed in, and was sent the verification email. The form is now checked against your global rules before the account is created, because the account doesn't exist yet. A refused address sees Access denied from your network address. Please contact your administrator. under the email field, as on the Sign-In screen. No account is created and no email is sent. Someone on an allowed address signs up as before. See How IP access control works.
  • For developers: POST /api/v1/web/login and POST /api/v1/web/register now follow your IP rules too. They issued a web token without checking them. The sign-in is checked before the password, against the account's own rules, then its roles', then the global ones, with the super-admin break-glass, exactly like the Sign-In screen. An email address that doesn't belong to an account gets the global rules. Sign-up is checked against the global rules before the account is created, after the Allow public registration check. A refusal answers 403 with error.code UNAUTHORIZED and Access denied from your network address. Please contact your administrator. It issues no token, creates no account, and doesn't say whether the email address is already registered. The web token still isn't accepted by the other /api/v1/web/… endpoints. See Authenticate API requests.

Core

Core 12.8.6

Signing up in the mobile app, and its two-factor step, follow your IP rules, and the API's IP refusal has an error code.

Fixed

  • When your IP rules refused a request from someone already signed in to the API, the answer was {"status": false, "message": "Access denied from your network address."}, the only API error without the standard envelope and an error code. It now answers like every other API error: 403, error.code UNAUTHORIZED, and Access denied from your network address. Please contact your administrator., the message a refused sign-in gets. An app or integration that read status reads error.code instead. See API errors and error codes.
  • The maintenance page's title is now saved under its correct name, maintenance_title. It was saved under a misspelt one, maintenance_tite. The upgrade renames your saved title, so your maintenance page keeps it, and nothing changes on screen. For developers: GET /api/v1/public/settings now has consent.maintenance_title, and keeps consent.maintenance_tite, with the same value, until the next major version. The older GET /api/v1/mobile/get_setting lists the row under its new name.

Security

  • Your IP rules now apply when someone signs up in your mobile app and when they enter their two-factor code there, as they already did to the app's password sign-in. Before, someone on a network address your rules refuse could create an account in the app and be signed in when they verified it, or finish at the two-factor step a sign-in they'd started from an allowed address. Signing up is checked against your global rules before the account is created, so a refused address leaves no account and gets no email. Entering the emailed code, and getting the first sign-in after verifying in a browser, are checked against the new account's own rules, then its roles', then the global ones. The two-factor step is checked again for the account signing in, before the code. A refused step gets Access denied from your network address. Please contact your administrator. and no session, and uses up no code, attempt or sign-up session: it works from an allowed network. Someone on an allowed address signs up and signs in as before, and the super-admin break-glass works as on the web. See How IP access control works and People can't create an account in the app.

Core

Core 12.8.5

The mobile app's sign-in follows your IP rules, and the admin's sign-in is no longer on your website's own address.

Fixed

  • With Google reCAPTCHA, Cloudflare Turnstile or hCaptcha set up and Fallback on Failure off, a provider's box that couldn't load in someone's browser, because a network or extension blocked it or the provider was down, left an empty space on the sign-in, sign-up or password-reset form, with no message, and the form couldn't be sent. Now the form says The security check couldn't load. Refresh the page or contact your administrator., in the same way it says the CAPTCHA isn't set up. With Fallback on Failure on, nothing changes: the built-in code stands in for the provider's box. See You can't get past the CAPTCHA.

Security

  • Your IP rules now apply when someone signs in to your mobile app with their password, and each time the app renews its sign-in, as they do on the web. Before, someone on a blocked network address, or outside your allow list, still got signed in to the app there. Laramin now checks the address before the password: the account's own rules, then its roles', then the global ones, with the super-admin break-glass as on the web. A refused sign-in gets Access denied from your network address. Please contact your administrator. and no session, and doesn't count as a failed attempt. Someone on an allowed address signs in as before, two-factor code included. See How IP access control works and Someone can't sign in to the mobile app.
  • When your public website has its own Site host, the admin and its sign-in now answer only on your Laramin's own address. Before, signing in, and the whole admin, also worked on the website's address. There they now show Page not found, like any page the website doesn't have. The website keeps working, and when Site host is empty or is your Laramin's own address, nothing changes. Sign in on your Laramin's own address. See Choose what your website's home page shows.

Core

Core 12.8.4

When the CAPTCHA can't work, the sign-in form says it isn't set up instead of showing a code that's always refused.

Fixed

  • With Google reCAPTCHA, Cloudflare Turnstile or hCaptcha chosen, no site key saved for it, and Fallback on Failure off, the sign-in, sign-up and password-reset forms showed Laramin's built-in picture. Only the provider's answer counts while Fallback on Failure is off, so the code people typed from it was refused every time, and nobody could get past the form. Now the forms say plainly that the CAPTCHA isn't set up and that people should contact their administrator, and show no code. An administrator saves the provider's site key, turns Fallback on Failure on, or chooses the built-in CAPTCHA. With Fallback on Failure on, nothing changes: the built-in code is shown and accepted, as in 12.8.3. See You can't get past the CAPTCHA and Set up CAPTCHA.

Articles this release changed

Core

Core 12.8.3

When the CAPTCHA provider's box can't load, the built-in code shown in its place lets people sign in.

Fixed

  • When your CAPTCHA comes from Google reCAPTCHA, Cloudflare Turnstile or hCaptcha and the provider's box can't load, or no site key is saved, the form shows Laramin's built-in picture instead, as long as Fallback on Failure is on. The code people type from that picture is now accepted. Before, Laramin checked it with the provider and refused it every time, so nobody could get past the form. Falling back never skips the CAPTCHA: the built-in code still has to be typed correctly, and only the picture shown to that person counts. With Fallback on Failure off, only the provider's answer counts, as before. See You can't get past the CAPTCHA and Set up CAPTCHA.

Articles this release changed

Core

Core 12.8.2

A new Laramin sends email, keeps people signed in from links, knows its own address and lets the mobile app sign in.

Fixed

  • Notification Manager can send email on a newly installed Laramin. Installing locked away the email details Notification Manager starts with, in a form Laramin couldn't read again, so none of its emails went out. On a Laramin installed before 12.8.2, whoever runs your server runs php artisan app:check-encrypted, which lists any saved details Laramin can't read and changes nothing. For each one, enter the details again on its screen and save. For Notification Manager that's Email Settings, under Notification Providers in Settings: on the SMTP tab, fill in every field, including SMTP Password, and select Save changes. See Notification Manager settings.
  • Laramin's own emails, such as password resets, use the mail server set in your server's settings file. Before, Laramin ignored the mail server's address there, so these emails didn't go out.
  • Following a link from an email or another website keeps you signed in. On a new Laramin, such a link opened the sign-in page and signed you out, and social sign-in couldn't finish. New installs now allow these links. On a Laramin installed before 12.8.2, open Developer Tools › Developer Settings › Session Settings, set Same-Site Cookie to Lax and save, unless your team chose Strict on purpose. See Someone can't sign in with a social account.
  • The web installer saves your site's address, the one you opened it at. Before, links in emails and some images pointed at http://127.0.0.1:8000. Installing from the command line, you can give the address with --url. On a Laramin installed before 12.8.2, whoever runs your server checks APP_URL, ASSET_URL and LOCAL_ASSET_URL in its settings file, then runs php artisan config:clear. See Install with the web installer and Install from the command line.
  • The mobile app can sign in on a newly installed Laramin. Before, every app sign-in failed with "Mobile authentication is not configured.", even with a wrong password. On a Laramin installed before 12.8.2, whoever runs your server runs php artisan auth:mobile-client --check. If it reports a problem, they run php artisan auth:mobile-client to set the sign-in up; running it again changes nothing. See Sign people in from a mobile app.

Core

Core 12.8.1

Scheduled jobs and background work, such as queued emails, run again, even when an add-on sets a schedule Laramin can't read.

Fixed

  • Scheduled jobs and background work run again. With the Blog or AI Manager installed, none of Laramin's scheduled jobs ran: queued emails and notifications waited, scheduled articles weren't published, reminders and backups didn't run. Now, if an add-on asks for a schedule Laramin can't read, Laramin skips only that job, notes it in the server log, and runs everything else. Updating the Blog to 2.4.1 and AI Manager to 2.3.1 fixes the same problem on any version of Laramin.
  • In Developer Tools › Scheduler, a job Laramin skips shows Not scheduled: invalid frequency, and a daily job shows the time it runs, such as Daily at 03:20.

Core

Core 12.8

The mobile app asks for your two-factor code, signs out for good, and can show your workspaces and what you may do.

New

  • The mobile app can list the workspaces you may work in, with each one's time zone and office hours. See Mobile API endpoints.
  • The mobile app can check what you may do in the workspace you're in, so it shows only what you can use. Laramin still checks every request.

Changed

  • When an app asks for a workspace or team the person can't enter, the answer now says so with its own code, so the app can show its workspace picker again. If you've built an app or integration that picks a workspace, handle the new answer. See Authenticate API requests.

Fixed

  • Someone who started signing up in the mobile app but didn't enter the emailed code in time can finish. They sign in with their password, and the app sends them a new code. See Let people sign up from a mobile app.
  • While Laramin is under maintenance, apps get a clear maintenance answer that says when it ends, so they can show a maintenance screen instead of an error. If you've built an app or integration that looks for maintenance, have it look for the new answer. See Turn on maintenance mode and API errors and error codes.
  • Phones on one office network or mobile carrier no longer share one allowance for staying signed in. If your Laramin is behind a load balancer or proxy, ask whoever runs your server to set TRUSTED_PROXIES. See API rate limits.
  • The mobile app no longer signs people out, or tells them their password is wrong, when sign-in is briefly unavailable on the server.
  • Changing the app's key no longer signs everyone out of the mobile app. See Register an API consumer and issue its key.

Security

  • The mobile app asks for the two-factor code of everyone who uses two-factor authentication, after their password or social sign-in. Require two-factor authentication applies to the app too. Update your mobile app before you upgrade: an older app can't finish signing in someone who uses two-factor authentication. After upgrading, whoever runs your server updates the database and ends the app sign-ins that were made without a code, as the upgrade notes describe; those people sign in again once. See Sign people in from a mobile app, Security settings and Set up two-factor authentication.
  • A temporary password, or one you've asked someone to change, doesn't work in the mobile app until they choose their own. Setting a password, a password reset and changing your own password on the web also sign the person out of the mobile app and stop their personal API tokens. Update your mobile app so it takes people to Forgot password when this happens. See Reset or set a user's password and Change your password.
  • Signing out of the mobile app ends that phone's sign-in completely: it can't sign itself back in. Your other phones stay signed in.
  • The mobile sign-in only tells someone who knows the password that an account is deactivated, unverified or without API access.
  • The mobile sign-in gives an app only the access a mobile app needs.
  • The mobile app's older settings list returns only public settings, never stored passwords or keys. If your app reads anything else from it, move it to the public settings before you upgrade. Whoever runs your server should run the check in the upgrade notes. If your mobile API could be reached by people outside your team before this release, they replace the passwords and keys it finds, and change the app's key only after upgrading. See Mobile API endpoints and Core Mobile configuration settings.
  • Every mobile address a module adds gets Laramin's own checks, such as the minimum app version and IP rules.
  • Permissions work the same in the mobile app as in the browser.

Core

Core 12.7

Open the Help Center from any screen at the right article, and sign in to see the docs for your own modules.

New

  • Open the Help Center from the ? icon in the header, or from Help Center in the account menu. It opens in a new tab at the article for the screen you're on. See Open the Help Center.
  • Sign in to the Help Center with your Laramin account to see the docs for the modules your Laramin has, including private docs for the people you allow. The Help Center shows the articles for your role first.
  • A new permission, Open the Help Center, decides who sees the Help link. Every role you have when you install 12.7 gets it. Roles you create later don't, so you add it when you want to.
  • Super admins connect your Laramin to the Help Center in Settings › General › Help Center. See Connect your installation to the Help Center.
  • Import Countries, States and Cities from a CSV file. See Import records from a CSV file.
  • Reset a user's two-factor authentication when they lose their authenticator app. See Reset a user's two-factor authentication.

Changed

  • The search box in the header reads Search…. It finds what your modules offer, not pages, users or settings.
  • If you belong to several workspaces and haven't chosen one, you sign in to the default workspace instead of being asked, when your Laramin allows it.

Fixed

  • Maintenance mode no longer locks out the people who can end it. The sign-in page stays open, super admins can still get in, and bypass addresses accept ranges. See Turn on maintenance mode.
  • Blocked IPs can block a range of addresses. The IP Range To box, which did nothing, is gone. See Block an IP address.
  • Automatic IP blocks lift when they expire.
  • Recent alerts shows alerts again.
  • Add-ons: Reset on a stuck add-on works, both ways of upgrading an add-on run the same checks, a system upgrade updates every module's data, and free add-ons are no longer marked as waiting for a license. See Run a system upgrade.
  • Every shortcut in the keyboard shortcuts list works.
  • Esc ends editing a cell in a list without saving, and edits in a cell save on every list.
  • The Import button only shows for people who may import.

Security

  • Require two-factor authentication now works. A team member who hasn't set up two-factor is asked to do so before they continue. Check who hasn't set it up before you turn it on. See Security settings.
  • A new web install no longer leaves the demo administrator account active. See Install Laramin with the web installer.
  • Paid add-ons need a real license key to activate.
  • The dashboard's people counts only show for people who may see the Users list.
  • Changes to security settings are written to the security log, and Clear log keeps the security log.

Core

Core 12.6

A multiple-choice list can show a second line under each option, such as a person's email under their name.

New

  • A multiple-choice list can show a second line under each option, such as a person's email under their name. Search finds an option by either line, and an option you've chosen shows only its name.

Core

Core 12.5.1

Amount filters keep "at least" and "at most", and you type amounts in the units the list shows, such as Lakh or Crore.

Fixed

  • An amount filter, such as a budget, can be set to at least or at most and keeps that choice. It used to jump back to between, and typing one side of a between range made the other box disappear.
  • You type an amount filter in the units the list shows. With Lakh selected, "40" means ₹40,00,000, and the full amount is spelled out under the box. You can switch a box to Crore. The filter chip shows the amount the way the list does, for example "₹ 40L–1Cr", and the match count updates as you type. See Filter a list.
  • Choosing an option from a dropdown inside a filter no longer closes the filter before you apply it.

Articles this release changed

Core

Core 12.5

Lists filter from a bar of plain chips above the table, and a filtered list keeps its filter in the page address.

New

  • Lists filter from a bar of chips above the table. The filters you use every day sit on the bar, ready to fill in, and any other filter is one + Add filter away (or press F). Each chip says in words what it filters on, shows how many records it will match before you apply it, and offers Undo when you remove it. See Filter a list.
  • When nothing matches, the bar suggests which filter to remove. A filter the list can't run says so on the bar, instead of the list quietly showing nothing.
  • A filtered list keeps its filter in the page address, so you can bookmark it or share it. If a filter is too long for the address, the list says so and suggests you save it as a view.
  • Build an "and / or" filter as a plain sentence, such as "Show inquiries that match all of these", in a panel beside the list, so the results stay in view.
  • Every kind of filter has an editor that suits it: a checklist for a short set of choices, a search for a long one, a from-to range for amounts, and "today", "this month" or a date range for dates. Is not works on choices too.
  • A list's search box says what it searches, for example "Search title, owner, phone…". You can also filter on something the list doesn't show as a column, such as a phone number.
  • Lists can find people by name, client code or phone number separately, and find a phone number however it was typed.

Changed

  • A column's own filter opens from a funnel icon in its heading, instead of a row of boxes under the headings. If you chose the row of boxes in the view settings, you keep it. See Customize the columns in a list.
  • The text in What's new and in the filters follows the text size chosen for your Laramin, and no label is smaller than 11 pixels.

Fixed

  • In Arabic, What's new shows the number in every count. Some counts spelled out the word for "one" and left the number out.

Core

Core 12.4

What's new replaces Version history: one feed of every update to your Laramin and its add-ons, newest first.

New

  • What's new replaces Version history. It opens on one feed of every update to the platform and the add-ons you use, newest first and grouped by month, with search, filters and a summary of recent changes. Each add-on also has its own history, and after an upgrade the versions just installed are marked New for you. See Check what's new in each version.
  • Add-ons are named the way your sidebar names them, in your language, in Addon Management, an add-on's details, What's new and the panel shown before an upgrade.
  • Release notes read as a headline and its detail, without links to code, tracker numbers or developer labels.

Changed

  • Release notes are grouped as New, Improved, Fixed, Being retired, Removed and Security.
  • What's new opens faster: it loads the first page of updates instead of every version of every add-on.

Fixed

  • Release notes are shown in full. About 300 notes that stopped after their first line now read to the end, and a release's breaking changes are listed again, under "Changes in how things work".

Articles this release changed

Core

Core 12.3.4

The horizontal menu keeps every item that fits, instead of folding down to one item and a "More" button.

Fixed

  • In the layouts with a horizontal menu, the menu keeps every item that fits. After you moved between screens, it could fold down to one item and More +7, however wide the window was.

Core

Core 12.3.3

Someone whose password an administrator set goes straight to the screen where they choose their own.

Fixed

  • When an administrator sets someone's password, that person is taken straight to the screen where they choose their own. They used to land on a half-loaded screen that showed the same "choose a new password" message on every click, with no way to the form. Add-on pages also ignored the requirement, and now wait until a new password is chosen.

Core

Core 12.3.2

A fresh install opens the web installer before any database is set up, instead of showing a server error.

Fixed

  • A new installation opens the web installer before any database is configured. Every page, the installer included, used to show a server error until the database details were typed into the environment file by hand.

Core

Core 12.3.1

Addon Management no longer reports a successful add-on upgrade as failed.

Fixed

  • Addon Management no longer says "Upgrade failed" after an add-on upgrade that worked. The upgrade always finished, database changes included, but the refresh at the end failed. The Refresh button and uploading an add-on's ZIP file failed the same way, and now work. See Upgrade an add-on.

Articles this release changed

Core

Core 12.3

"Discard changes?" is asked only about the screen you're leaving, not about forms left open in the background.

New

  • An add-on can add an icon link with a count to the header, next to the Website link. It's there only while the add-on is enabled and only for people who may open it. It opens inside your Laramin, and no page waits for its count to load.
  • An add-on's link in the account menu can have its own icon.

Fixed

  • Discard changes? is asked only about the screen you're leaving. A form left open in the background used to make every move, anywhere in your Laramin, ask about changes you couldn't see.
  • A screen can use your microphone and your location when it asks for them, for example to record a voice note or to center a map on where you are. The browser used to refuse both without asking. Content from other sites embedded in a page, and your public website, still can't use them.
  • An add-on's header link now appears, and opens inside your Laramin instead of reloading the page.
  • The sidebar highlights the item that best matches the page you're on, not the first one that partly matches.
  • A block editor cleared at the same moment it's unlocked stays cleared.

Core

Core 12.2

Choose which experiences each user may enter on the Users form. The Administrator role no longer grants them.

New

  • Choose which experiences each user may enter, on the Access step of the Users form. See Choose which experiences a user can enter.
  • Entering an experience, from the sign-in chooser or the header's View switch, opens that experience's home page.
  • Choose which module page your public website opens on, in Configurations › Security › Public website. If that page's module is disabled, the website falls back to the default page and the panel tells you. See Choose what your website's home page shows.
  • Your website's pages can show content published in a content space you choose, with the Content space setting.
  • A plain, branded default page for your website's main address, with the product's name and version. It loads no scripts and sets no cookies, and you can edit its search description.
  • An App icon in System settings. Browser tabs, phone home screens and the install prompt show your product's name, colors and icon, or a generated monogram until you upload one. See System and company settings.
  • Schedule follow-up in a list row's menu, when an add-on provides follow-ups and you may schedule them.
  • Forms can have file upload fields with their own formats and size limits, alt text for uploaded images, placeholder text, and email and web-address fields that check for a real address. A single-language text field can offer Ctrl+G phonetic typing, and a drawer form can have one language switcher for the whole form.
  • File sizes in File upload settings are typed as a number with a KB, MB or GB unit beside it.
  • Lists: reorder rows from the keyboard with Move up and Move down or Alt+Arrow keys, open a record by clicking its row or pressing Enter, and on a phone, press and hold to select a card. Some columns hide by default on smaller screens.
  • Saved views that an add-on provides show their name in your language. See How saved views work.
  • Issue, rotate and revoke an API consumer's key from the admin. A new key is shown once.
  • An add-on can refuse to be uninstalled and explain why, with choices. An add-on whose data is archived on uninstall has its tables exported before anything is removed. See Disable or delete an add-on.
  • A message can offer two actions, and show how long you have to use one, such as Undo.
  • On a phone, the page header fits on one row.

Changed

  • The Administrator role no longer lets people enter experiences. Which experiences a person may enter is chosen per user. Everyone who could enter one through the role keeps that access in each workspace they belong to, so nobody loses access.
  • The coming-soon page uses the same design as the default page.

Removed

  • The placeholder app icons. If your Laramin was installed by copying files to the server, ask whoever looks after the server to delete the old favicon and icon files listed in the developer changelog, or browsers keep showing the old blank icon.

Fixed

  • Opening a notification in the header panel marks it as read. See Read your notifications.
  • API Consumers and Public website are in the sidebar, under Developer Tools and Security. You used to have to type their address.
  • The header's Website link appears.
  • The cookie banner can be dismissed, and follows the visitor's answer.
  • Browser tabs show your icon instead of a blank one.
  • The admin's main address, and the logo in the header, open the page you land on after signing in, instead of "Screen not available".
  • Saved-view counts no longer read 0 on lists inside a record.
  • In Arabic, counts above one use the right plural form.
  • Installing, enabling or upgrading an add-on no longer rewrites the translations of Core and the other add-ons, or loses Core's menu labels.
  • A failed add-on install no longer leaves the add-on enabled with its menus.
  • A role that may create or edit records, but not see their list, can open the form.
  • Saving a drawer shows one loading indicator, not two.

Security

  • Self-registration from the website is off by default, and Allow public registration in Security settings really controls it. If your Laramin had turned it on, it stays on. Turn it on if you rely on open sign-up.
  • The web API's list of users needs the permission to list users, feature.core.user.list. Before, any signed-in session could read every user's name and email. Give that permission to any API client that reads the list.
  • Super admin accounts are hidden from anyone who isn't a super admin: in the Users list, its counts, search and export, and in the web API. See Super admin vs Administrator.
  • Responses no longer reveal the server's PHP version.
  • An App icon upload that claims an oversized image is refused before it's processed.

Core

Core 12.1

Each workspace has its own time zone, and you see times in your own zone with the workspace's clock beside them.

New

  • Set a workspace's time zone on its own form. Laramin asks you to confirm before you change it. See Create a workspace.
  • "Today", working days and due times follow the workspace's time zone. You see times in your own time zone, with the workspace's clock beside a business time. See Update your profile.
  • Company settings have an Office Hours section, with hours for each day. See System and company settings.
  • A Website link in the admin header opens your public website.
  • With an add-on that provides follow-ups, you can schedule, complete and snooze a follow-up from a record's own screen, see the work still outstanding on a record, and snooze to the business's next working day.
  • An access matrix shows what each role may do, and changes to a role's permissions are recorded.
  • Step-by-step forms show your progress as a gauge, and keep every step's description on screen.
  • Animations stop when your device asks for reduced motion.

Fixed

  • A time picker's Today button sets the current time.
  • A browser tab left open during an update reloads once, instead of showing a broken screen.
  • The rich-text editor no longer turns every space into a non-breaking space.
  • If the database stops responding, pages show an error instead of loading forever.
  • In step-by-step forms, Save works again when everything is valid, the step list shows where you really are, and a blocked step's message no longer replaces Cancel.
  • A list remembers its row density only when you chose one.
  • The public website settings and the coming-soon page are translated.

Core

Core 12.0

Workspaces arrive: run several businesses in one Laramin, each with its own teams, roles and settings.

New

  • Workspaces: run more than one business in one Laramin, each with its own people, teams and settings. See Workspaces, teams and experiences: the basics.
  • Every team belongs to one workspace. See Create a team and add members.
  • A role can apply in one workspace instead of everywhere.
  • Experiences replace user types. An experience decides the menu, the layout and the home page you see. Switch experience from View in the header, and set a default. See Switch to another experience.
  • The admin's look comes from Appearances. See Customize the admin's appearance.
  • An add-on's details show which other add-ons, and which versions, it needs. An add-on can't be enabled while something it needs is missing, and one whose needs aren't met stays off and says why, instead of causing errors. See Add-on statuses and actions.
  • An empty menu says so, instead of staying blank.
  • A dropdown can create the option you're looking for, and an option you can't pick shows as unavailable instead of disappearing.

Changed

  • User types are gone. If your Laramin customized a user type's home page, menu or layout, those settings are ignored now: an experience does the same job. The permissions for user types no longer do anything.
  • A role given in a team adds to what the person may do everywhere. It no longer replaces it. To give someone less in a team, remove the broader role.

Fixed

  • The sidebar no longer offers screens you can't open.
  • The workspace switcher is hidden when there's only one place to go, and the team switcher shows just its icon.
  • The header switchers and the color picker work again.
  • A problem with one field's options no longer breaks the whole Users screen.
  • IP rules that name a role look at the roles a person holds everywhere, not roles given only in a team.