Audience: Chemist administrators, lab operations / system owners, and super users who configure Albert workspaces.

The Settings page is the central place for admins and key super-users to manage workspace access and configuration in Albert. Use it to:

• Control who can access Albert (Users, Teams, Roles)

• Maintain configuration needed for your workflows (PDF Labels, and (if enabled) Custom Fields, Custom Task Types, Custom Report Types)

On this page

• 👥 Who should use this?

• 🧭 How to open Settings

• 👤 Account

  • 👤 Users

  • 👥 Teams

  • 🛡️ Roles

• 🧩 Configurations

  • 🧾 PDF Labels

  • 📚 Custom Fields, Task Types & Report Types

• ⚡ Workflows & Playbook

Settings is primarily for:

• Chemist administrators

• Lab operations / system owners

• Super users who configure Albert for multiple teams

1. In Albert, click your name initials in the top-right corner (example: “MN”).

2. Select Settings.

You’ll land on a page with a left-side navigation.

The Manage People & Roles page has moved and makes up the account section. Users, Teams, and Roles each have their own tab for simplified management, and core functionality of each remains the same.

Use Users to manage who can sign in and what access they have.

Common actions

• Add a new user to the workspace

• Update a user’s access level / role

• Deactivate users who no longer need access

When this is helpful

• A new chemist joins your team and needs access quickly

• Someone changes teams and their permissions need to change

• You want to keep access clean for compliance and audits

Use Teams to organize people in a way that matches how your lab operates.

Examples of team structures

• By function: R&D, Analytical, QA/QC

• By program: Coatings, Personal Care, Battery Materials

• By site: Site A, Site B, External collaborators

When this is helpful

• Ownership and responsibilities stay clear even when projects involve multiple groups

• It’s easier to onboard people consistently by assigning them to the correct team

Use Roles to control permissions and responsibility boundaries.

Best practices

• Keep admin/configuration capabilities limited to a small set of owners

• Use roles to standardize permissions across teams and sites

• When unsure, start with least access and expand as needed

When this is helpful

• Prevent accidental configuration changes

• Make audits and handoffs easier (clear “who can change what”)

Configuration pages help standardize how data is captured and shared across your organization. This is especially valuable when multiple chemists and teams work in the same workspace.

The PDF Labels page shows the labels that Albert has created for your organization. These labels are used in PDF outputs to keep terminology consistent across projects and teams.

At this time, you cannot create or upload your own labels from this page. It is an overview of the labels currently available in your workspace, not a configuration screen.

What this page is useful for

• Seeing which labels are available in exported PDFs

• Checking that naming matches your internal terminology

• Identifying labels that may need to be added, renamed, or retired

Use cases

• Standardized labeling for samples/batches

• Cleaner exports for internal reviews and external sharing

• Reduced manual edits after exporting PDFs

Admin tip
If you need new labels or changes to existing ones, reach out through your usual Albert Support channel.

These Settings pages are for future expansion. Today, they provide high-level overviews of features that are already available in Albert, even though they cannot be configured directly from these pages.

Use them to understand what each feature does and whether it might be useful for your organization. For configuration, contact your Albert administrator.

Custom Fields let your organization add structured metadata, so teams record the same critical details every time.

Use cases

• Track equipment/instrument IDs

• Capture supplier lot, grade, or internal classification

• Add consistent tags used for filtering and reporting

• Reduce variation caused by free-text entries

What good looks like

• Use dropdowns when values repeat (better filtering, fewer typos)

• Assign an owner to maintain and review fields

• Keep the number of fields manageable (avoid “field sprawl”)

Custom Task Types help you standardize how work is executed by defining repeatable task structures that match your lab’s real process.

Use cases

• Standardize a common lab procedure so every run follows the same structure

• Reduce one-off work and inconsistent documentation

• Make reviews easier because tasks look consistent across teams

Admin tip
Start with your top 5–10 recurring task types, then expand based on feedback.

Custom Report Types standardize report outputs, so teams generate consistent exports for stakeholders and audits.

Use cases

• Consistent reporting for review meetings and leadership updates

• Standard format for cross-team comparisons

• Audit-friendly documentation with fewer missing sections

Admin tip
Create one “default” report type that works for most projects, then add specialized versions later.

• Review active users

• Deactivate people who no longer need access

• Confirm admin roles are limited to owners

• Create the team (if needed)

• Add users and assign roles consistently

• Confirm permissions are correct before project work starts