Dear @Kennedy, Chelsey, FFTMEC,
Thank you for posting your question in the Microsoft Q&A forum.
I understand how inconvenient it is to publish a shared Bookings page and then suddenly find yourself listed only as a Team member, especially when the page shows no administrator assigned.
When a shared Bookings page is created and you add yourself during the Invite staff step, the system normally assigns the Administrator role automatically and does not allow it to be changed. However, a few factors can unexpectedly cause your role to switch to Team member. This can happen if your Exchange mailbox permissions are modified, if you were added to the page by typing your email instead of selecting your account directly from the directory, or if your account type or license was changed.
In Microsoft Bookings, only users with administrator‑level access can edit page settings and staff roles. Team member, Scheduler, Viewer and Guest each have limited permissions, which is why the loss of the Administrator role prevents you from managing the page.
- To restore access, you will need assistance from your organization’s IT administrator:
Each Bookings page is backed by an Exchange shared mailbox, and your IT admin can assign you “super user” access by granting FullAccess and SendAs permissions through Exchange Online PowerShell. These permissions will restore your ability to manage the Bookings page without adding you as bookable staff.
This article provides further guidance on the topic: Add team members to Bookings | Microsoft Learn
Once your IT admin has applied these permissions, please sign in to Bookings again, open the shared page, go to the Staff section and update your role to Administrator.
If the role still cannot be changed after these steps, there are unfortunately no additional methods available to recover administrative access on that specific page. In such cases, the only solution is to create a new shared Bookings page. When setting up the new page, I strongly recommend assigning at least two users as Administrators to prevent the same issue from happening again.
As community moderators, we kindly ask for your understanding that our access to internal development details is limited. Our primary role is to guide users toward the appropriate resources and support channels. While we may not have visibility into performing deeper backend analysis, we’ll continue doing our best to support you within the scope of our responsibilities.
I hope this information is helpful. If you have any questions or need further support, please don’t hesitate to reach out at any time.
Thank you for your patience and understanding.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have any extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.