Skip to content
All products
22PasswordsPreviewProduct overview

Shared credentials for the team · Preview

The right code for the right person.

Keep door codes, alarm codes and shared logins organised by Site, area and function. Give each team access to the entries they need for service, with deliberate, timed reveal.

Available in preview

Available in enabled pilot workspaces. Sign in online to open the collections your business has assigned you. The public example uses fictional data.

See what’s next

More of the work, connected.

See what you can get done.

During servicePreview

Music, tills and shared logins, easy to find.

Use area and function together to get to the entry that belongs to the job in front of you.

  • Filter Bar and Music independently.
  • Keep metadata access and reveal permission separate.

Labels organise records. The entry's current audience controls access.

Read the guide
During serviceFictional example
Bar · MusicFind the login. Keep service moving.
  • SpotifyNorth Quay · Bar leads
  • Reveal, then hideOne value, a short window and a visible countdown

Area and function narrow the list. Current access decides which entries appear.

A fictional Spotify entry with a Site-scoped audience.

Changing accessPreview

Keep the keys with the current team.

Review access when staff leave or responsibilities change, then replace credentials at the source where needed.

  • Revoke access through People and access.
  • Use permitted activity to review credentials that need changing.

Saving a replacement in Soupy records the change. The external alarm, door or service needs its own change.

Read the guide
Changing accessFictional example
People and accessKeep access current when the team changes.
Revoke
Remove the person’s scoped access.
Review
Check relevant reveal activity with current authority.
Replace
Change the real credential at its source, then save its replacement.

Illustrative manager workflow. This example changes no account or credential.

An illustrative offboarding sequence, with no live account changes.
Explore the workspaceApp preview

Explore fictional Site-scoped collections and deliberate timed reveal. This sample runs locally and uses no live credentials.

Current workspace layouts with sample data. Nothing is saved or sent.

Product preview · sample data
MD
Example Hospitality Ltd. / Demo venue / Passwords

Passwords

Fictional entries across your authorised Sites.

Preview

North Quay · Door Codes

Staff entrance

Front of house

Fictional value••••••••••••
Duty managers

Explicit collection audience · North Quay

Area and function organise entries. Access is granted separately.

Fictional Passwords example. Filters and timed reveal run locally with made-up values. No live credentials or access changes are involved.

On the other side of the shift

Less friction. More getting on with it.

  1. 01

    Find the right code before the doors open.

  2. 02

    Give each team an explicit audience for its credentials.

  3. 03

    Organise by area, function or both.

What’s included

Made for the job.

The practical details behind the promise. Built around the people doing the work, and connected to the information they need.

  1. 01

    Find it where you work

    Start with all authorised Sites, then narrow by Site, physical area or function. Door Codes, Alarm Codes, Music, EPOS and PC Logins keep different jobs easy to find.

  2. 02

    Access follows the audience

    Each collection has an explicit Site-scoped audience. Viewing an entry, revealing its value and managing access are separate permissions.

  3. 03

    Reveal when you need it

    Values start masked. An eligible person deliberately reveals one value for a short time, with a countdown and a Hide now action.

  4. 04

    Keep codes current

    Replace a credential after changing it at the source. Retire entries that are no longer used and review safe activity records without displaying their values.

More of the working product

What you can do with Passwords.

Explore the tools behind the overview, then open a workflow for the steps, settings and availability that apply. Product access, rollout and connected providers determine what your workspace can use.

Organised for service

  • Codes and shared logins in Site-scoped collections.
  • Independent Site, area and function filters.
  • Search within the entries you can view.

Prepared preview. Classification carries no access authority.

Explicit team access

  • Named collection audiences within the current business and Site.
  • Separate permission to view, reveal and manage.
  • Current admission checked for each protected action.

Changing a job title or category never grants access.

Deliberate reveal

  • Masked values until an authorised reveal.
  • A short display window and Hide now.
  • Safe activity records without secret values.

Real use requires online service readiness and acceptance.

Keep entries current

  • Replace a saved code after changing it at the source.
  • Retire an entry when the team stops using it.
  • Review scoped activity after a handover.

Changing a saved value does not change the source system.

Explore every workflow in the guides.

Choose a guide to see all its topics. The detailed guides include setup requirements, preview features and supported limits.

Passwords3 workflow topics

Find shared venue credentials by Site, area or function and reveal one with current access. Preview for enabled businesses.

Read the complete guide

Part of the bigger picture

The context comes with it.

The guest, the venue, the team. Useful information should follow the work. Passwords connects to shared records, with access controlled for your organisation and your people.

Passwords
Shared recordsSites and areasPeople and accessScoped activity

A clear picture

Today. And what’s next.

Available in preview

Available in enabled pilot workspaces. Sign in online to open the collections your business has assigned you. The public example uses fictional data.

Product direction

Native device acceptance, stronger device protections and supervised migration are separate delivery steps. Capture protection remains platform-dependent.

Good questions

Passwords FAQs.

Can I organise by area and function together?

Yes. Area and function are independent filters, so you can find Music in the Bar or Door Codes across authorised areas. Classification never grants access.

Does every manager see every password?

Access is explicit for each collection and Site. Metadata, reveal and access management have separate permissions, and every action checks the current scope.

What happens when someone leaves?

Revoke their access through People and access. Review credentials they previously revealed and change the real codes or passwords at their source where needed.

Does saving a new value change the alarm or service?

Change the credential at the alarm panel, door controller or service first, then record the replacement in Soupy.

Can screenshots be blocked?

Protection depends on the app, operating system and device. This preview makes no capture-blocking guarantee. Access controls and deliberate reveal remain the core protections.

Start with the pressure point

Explore the Passwords preview.

Try Passwords