Applicable plans: ❎ The free plan, ❎ The complete plan

You want to use Waldo, but keep its interaction with Microsoft 365 as light as possible? Good news, Waldo adapts its permission scope to your exact needs 💡.

Depending on how you plan to use Waldo, you can choose a minimal setup without compromising the experience.

Scenario 1: A small user group with simple booking needs

You’re deploying Waldo for a limited group (around 100 users) and only need basic features:

• Desk booking
• Parking booking

No meeting room booking, no Outlook synchronisation, no advanced user management or emergency features.

What to do:

Go to Admin consent page and enable Default features only. Make sure all other features are disabled.

Required permissions (3 scopes):

• User.Read: Retrieve user information
• User.ReadBasic.All: Retrieve basic information for all users
• Chat.ReadBasic: Identify teammates during onboarding

Scenario 2: A larger deployment with light administration

You’re rolling out Waldo to a bigger group (100+ users), but still want to keep things simple, no advanced room booking or complex features.

In this case, we recommend adding a bit of structure:

• User management (to hide inactive users)
• Filtering users via Azure Groups

Required permissions (6 scopes):

• User.Read: Retrieve user information
• User.ReadBasic.All: Retrieve basic information for all users
• Chat.ReadBasic: Identify teammates during onboarding
• User.Read.All: Retrieve detailed user information
• Place.Read.All: Exclude meeting rooms from user lists
• Directory.Read.All: Filter users using Azure Groups

This setup gives you better control while keeping things lightweight ⚖️

Data privacy by design

⚠️ Important: Waldo does not store any personal data. No first names, no last names, no emails.

Our architecture is designed with privacy in mind from day one — minimal permissions, minimal data, maximum peace of mind 🔐.

Need help choosing the right setup? Start simple — you can always scale later.