Microsoft Loop advanced settings: how to find them

Microsoft Loop settings are split across the app, the page or workspace you’re working in, and Microsoft 365 admin controls. If you’re a normal user, you can usually change personal behavior like notifications inside Loop; if you’re an admin, the broader sharing and availability rules usually live in Microsoft 365, not in Loop itself. If a setting is missing, greyed out, or behaves differently on another device, the cause is often permissions, tenant policy, or rollout timing rather than a broken app.

Prerequisites

• Access to Microsoft Loop, signed in with the account you want to change.
• The right role in Microsoft 365 if you need to change tenant-wide settings.
• Access to the page or workspace you want to manage, if the setting is tied to shared content.
• A second device, browser, or user account for testing changes if you need to confirm access or notifications.

What you can and can’t change in Microsoft Loop

Before you click around, separate Loop controls into three groups.

User-level preferences are the settings you can usually change for your own experience, such as notifications or display-related behavior. These affect how Loop looks or alerts you, but they do not usually change what other people see.

Workspace and page controls affect sharing and collaboration on a specific workspace or page. These are the settings that decide who can access content, who can edit, and how broadly a page can be shared.

Tenant-level admin settings live in Microsoft 365 admin controls, not in Loop itself. These are the policies that can allow or block Loop features across the organization, such as whether Loop is available at all, whether external sharing is allowed, or whether certain Microsoft 365 security controls apply.

A practical rule: if the change affects only you, look in the app. If it affects sharing or access for a page or workspace, look at the item controls. If it affects what users in the organization can do everywhere, an admin setting is usually behind it.

Where to find the settings people usually miss

Most users start in the Loop app, but some of the settings people call “advanced” are in Microsoft 365 or are controlled outside Loop entirely.

Start in the Loop app itself. Look for the settings area in the app’s main menu, profile area, or account controls. That is where you would expect personal preferences such as notifications or app behavior.

Then check the page or workspace sharing controls. In many cases, the option you want is not a global app setting at all. It is on the page, workspace, or share panel for that specific item. If a page can be shared but a workspace cannot, the difference is usually in the permissions model, not in a hidden preference.

For tenant-wide controls, use Microsoft 365 admin tools. Depending on your role, that may mean the Microsoft 365 admin center or the relevant Microsoft 365 app or service settings that govern Loop availability and collaboration behavior.

If you are not an admin, you may be able to see that a feature exists without being able to change the policy behind it. That is normal in managed Microsoft 365 environments.

How to change the settings that matter most

The settings people most often want to change are notifications, sharing, page access, and workspace behavior. The exact labels can vary a bit by rollout, account type, and device, but the path is usually straightforward once you know which layer you are changing.

1. Open Loop and go to your account or app settings.
2. Look for notification-related options and change the alerts you want to receive.
3. Save the change, then refresh Loop or reopen it so the new preference loads.

If your goal is sharing, open the page or workspace you want to adjust.

4. Open the share or permissions panel for that page or workspace.
5. Choose who can access it: specific people, people in your organization, or anyone allowed by policy.
6. Adjust edit rights if the option is available, then copy or resend the sharing link.

If you manage collaboration defaults for a team, check the workspace settings or the admin policies that govern collaboration. For example, if your company wants people to work inside a shared workspace instead of sending one-off pages, the workspace permission model should support that. If it does not, the blocker is usually a broader policy or a missing permission, not a setting hidden deeper in Loop.

When a setting controls access, test it with a simple case. Share a page with one coworker, then confirm they can open it with the rights you intended. That tells you more than trusting the menu label alone.

Which “advanced” options are real settings

Some options people expect to find in Loop are not really settings at all. They usually fall into one of these groups:

• Real app settings: personal preferences such as notifications or display-related behavior.
• Permissions: who can view, edit, or reshare a page or workspace.
• Tenant policies: Microsoft 365 rules that allow or block a feature across the organization.
• App behavior: things that look like settings but are controlled by rollout timing, browser state, or the account you’re signed into.

That distinction matters because the fix is different for each one. If a control changes only your experience, it belongs in the app. If it changes who can see or edit content, it is usually a permission. If it affects the whole organization, it is usually a tenant policy.

Why a setting might be greyed out or missing

A missing or greyed-out setting usually means one of a few things.

• Your account type does not support that control.
• You do not have the right role in Microsoft 365 or in the workspace.
• Your organization has turned the feature off with policy.
• The feature is still rolling out, so you see it on one device or tenant but not another.
• The setting exists, but another Microsoft 365 control overrides it.

A greyed-out sharing option often points to permissions. For example, if you can view a page but cannot change who can edit it, you may have read access only, or the workspace owner may have restricted sharing.

A missing notification setting often points to app scope or rollout. You may be looking in the right place, but the option is not available in your build, browser session, or tenant yet.

A setting that looks available but does nothing usually points to a policy conflict. For example, you might change a page-level sharing choice, but the tenant blocks external sharing, so the page still behaves as if the stricter rule is in force.

If you are an admin, confirm the user has both the correct Loop access and the Microsoft 365 permissions behind the feature. If you are not an admin, ask for the exact role or policy name that may be limiting the setting.

How to check whether the change worked

After you change a setting, verify it in more than one place.

1. Refresh Loop or close and reopen the app.
2. Check the same setting again to confirm the saved value is still there.
3. Open Loop on a second device or in another browser session if you use more than one.
4. Test the behavior that should have changed, such as a notification, share link, or page access permission.
5. Ask a second user to confirm what they see if the change affects shared content.

If the setting is about notifications, wait for the next expected alert or check the notification area tied to the app or Microsoft 365 account.

If the setting is about sharing, use a test page and confirm the invited person can open it with the right access level.

If the setting is about workspace controls, verify that the workspace still shows the intended members, roles, or edit access after you reload the page. The change is real only if it survives a refresh and matches what other users see.

What to do if Loop still acts the same after you change it

If Loop still behaves the old way, start with the simplest cause first.

Clear the browser cache if you use Loop in a browser, then sign out and back in. Cached data can keep old behavior alive even after the setting has changed.

Check another device or browser profile. If the setting works there, the problem is local to the original session or cache.

Look for a conflicting Microsoft 365 policy. A tenant-level rule can override what you set in Loop, especially for sharing and access.

If the issue affects only some users, compare their account type, license, and role. Different users can see different controls in the same tenant.

If the issue affects everyone, ask an admin to confirm that the change was made in the correct Microsoft 365 control area and that the policy has finished applying. Some changes are not immediate across every client.

If you still cannot make the setting stick, capture the exact page, workspace, or policy that seems to override it and hand that to your Microsoft 365 admin. That is usually faster than trying to troubleshoot from the Loop screen alone.

Conclusion

The fastest way to manage Loop is to treat it as a three-layer product: your personal app settings, the page or workspace controls, and the Microsoft 365 policies behind them. Once you know which layer owns the change, the rest gets much easier. If a setting still looks wrong after you save it, verify it in a second session and compare it with the tenant rules that may be overriding it. That will usually tell you whether you need to adjust Loop, change a Microsoft 365 policy, or hand the issue to an admin. For a final check, look for the saved value in the same menu, then test the actual behavior on another device or with another user.

Frequently Asked Questions

Why can I see a Loop setting on one device but not another?

That usually means the feature is being rolled out unevenly, the app session is cached, or the two devices are signed into different account types or tenants. Check after a refresh, sign out and sign in, and compare the same Microsoft 365 account on both devices.

Can a Microsoft 365 admin control Loop sharing for everyone?

Yes. Sharing behavior is often governed by Microsoft 365 tenant policy, not just a Loop page setting. If an org blocks external sharing or limits collaboration, that policy can override what you set inside Loop.

Why is the page access option greyed out?

The most common reasons are missing permission, a restricted workspace role, or a tenant policy that limits who can change access. If you can view the page but not edit sharing, your account likely does not have enough rights.

How do I know if my change actually saved?

Reload Loop, return to the same setting, and test the affected behavior on another device or with another user if possible. If the setting reverts after refresh, a policy or sync issue is usually involved.