Good to know

Design decisions that follow from running without a server and from how SharePoint works. Knowing them helps you plan.

• Background jobs need an admin visit. The scheduled sync and the daily reminders run when an admin opens the directory. If no admin visits for a while, they wait until the next visit.
• Email comes from people's own mailboxes. Event emails come from the person whose action triggers them. Reminders come from the admin whose browser runs the check. With Enterprise, a shared mailbox can be used instead. There is no separate service account.
• "HR only" is an in-app control. The employee list must be readable by every directory user, so values marked "HR only" are hidden in the app but are not protected by SharePoint permissions. Keep confidential HR data in your HR system.
• Notification text is readable by list users. Notifications are created by one person for another, so keep sensitive details out of notification templates.
• Site owners are always directory admins. This is how SharePoint permissions work: anyone who owns the site can change its lists.
• Graph permission approval is tenant-wide. In Microsoft 365, approving a permission for SharePoint Framework solutions makes it available to every SPFx solution in the tenant.
• Language. The interface is in English. Date and time formats are configurable.
• Size. People are loaded and searched in the browser, which is designed for organisations of up to roughly 10,000–20,000 people.