Most issues with users logging into Fellow and granting permissions to sync their Microsoft calendar stem from configuration settings in Microsoft Entra. The most common symptom is users receiving an error message requesting admin approval - sometimes with a Request Access option, and sometimes with no options at all.

The steps below cover the recommended configuration to resolve these issues.

Even if users cannot grant consent themselves, they should be able to request it through Microsoft Entra's built-in admin consent workflow. Once configured correctly, users will see a Request Access button when they encounter a permission error.

In Microsoft Entra, navigate to: Enterprise applications > Consent and permissions > Admin consent settings.

Ensure that Admin consent requests are enabled.

For full configuration details, see Microsoft's guide to setting up an admin consent workflow.

Microsoft Entra controls when end users can grant consent to applications on their own, and when admin approval is required. Misconfiguration here is the most common cause of login issues with Fellow.

In Microsoft Entra, navigate to: Enterprise applications > Consent and permissions → User consent settings

There are three options:

Option 1: Allow user consent for apps (Easiest) Allows users to consent to any app. Gives users the most control but carries additional risk depending on your organization's compliance requirements. Recommended for smaller organizations without stringent policies.

Option 2: Allow user consent for apps from verified publishers, for selected permissions (Best for security) Limits consent to verified publishers for permissions classified as Low Impact. Fellow Insights Inc is a verified publisher in the Microsoft ecosystem. If you choose this option, you must manually classify all Fellow permissions as Low risk - see Step 2A below.

Option 3: Do not allow user consent (Not recommended) Prevents users from installing any application. If this is selected, you must either enable admin consent requests (Step 1) or grant admin consent for the entire tenant (Step 3).

For more details, see Microsoft's guide to configuring user consent settings.

Note: This step is only required if you selected Option 2 in Step 2.

In Microsoft Entra, navigate to: Enterprise applications > Consent and permissions > Permission classifications

Ensure all permissions required by Fellow are present under the Low tab. For each permission, the API used column should show either Fellow.app or Microsoft Graph.

The core required permissions are: offline_access, openid, profile, User.Read, Calendars.ReadWrite. Additional permissions are required if the Microsoft Teams integration is installed. See the full list in the Microsoft 365 API Scopes article.

To add any missing permissions:

The list of permissions may vary depending on your configuration (for example, if the Teams integration is installed).

For more details, see Microsoft's guide to configuring permission classifications.

Note: This step is optional but recommended if Fellow is being rolled out organisation-wide, or if you want to ensure all invited users can access Fellow without hitting permission errors.

In Microsoft Entra, navigate to: Enterprise applications > All applications > Fellow.app

Click Grant admin consent. A new window will open prompting you to grant the required permissions. Before doing this, ensure you are logged in as a Fellow workspace administrator in the same browser.

Review the list of permissions and click Accept. The specific permissions shown may vary depending on your workspace configuration.

Need further help? Contact the Fellow support team at [email protected] or use the chat bubble in the bottom corner of the screen.