Built-in App Access

Choose who can use each app.

Make an app public or restrict access to selected people and teams. Connect your company's login and give users one place to find the applications they can use.

Put an app to work with the right accessRead about app access
purchases.acme.shpyrd.app

Sign in to open Purchase requests

Finance and Operations can open this app.

The right people open the right apps.

An app restricted to a team, and a site anyone can open.

  1. Step 1

    Sign in with your company's login

    A person signs in through single sign-on (SSO), where it is set up.

  2. Step 2

    Open the app from the portal

    The portal lists the apps that person may open.

  3. Step 3

    Or open it to everyone

    A public site needs no invitation: visitors just open it.

What makes it work

  • Public or sign-in required. Choose for each application.
  • Company sign-in. Through supported identity providers.
  • People, teams, and roles. Separate permissions to use an app, view its management information, publish changes, and administer.
  • An app portal. One place where people find the apps they can use.
  • Identity for your app. Who is signed in is made available to the application, for supported integrations.
acme.shpyrd.app

Your apps

Signed in as luis@acme.com

  • Purchase requestsOperations
  • Onboarding checklistPeople
  • Quote toolSales
  • Field reportsOperations

Practical questions

Does access control what people can do inside the app?

No. Shpyrd controls who can open the app and tells it who they are. Actions inside it, like approving a payment, are your app's to define.

Can we use our company login?

We can confirm SSO support for your identity provider and the offer that fits your setup.

Can an app be open to the public?

Yes. Make it public and anyone with the link can open it.

Use your company's login. Give people the apps they need.

Make an app public, or choose the people and teams who can use it.

Put an app to work with the right access