If you are getting email or in-app notifications about conversations that belong to another property, your own access is usually not the cause. Bookboost already scopes incoming messages to the properties you have been given access to, so a conversation from elsewhere almost always reaches you through a team you belong to. The fix is to change the team's scope rather than your own permissions.
Teams have their own scope
A team is scoped either to your whole organisation or to a single property.
A property-scoped team only ever picks up conversations from its own property, and only operators who have access to that property can be in it.
An organisation-scoped team picks up conversations from any property in the organisation, and passes them to every member.
Every team created before property scoping was introduced is organisation-scoped. That is the usual reason a conversation from a property you do not work in still lands in your notifications: you share an organisation-scoped team, or a catch-all team for messages that have not been routed anywhere else, with operators from other properties.
This is separate from what you can see in the Unified Inbox day to day, which follows the properties assigned to you. See Property-level data visibility in the Unified Inbox for what that covers.
Step 1: Find out which teams you are in
Go to Inbox > Inbox settings > Teams.
Look through the list for the teams that include you.
Check the scope of each one. A team set to the organisation is the one to look at first.
The Teams section is visible to admins. If you are not an admin, ask one in your account to check this for you.
Step 2: Re-scope the team to the property
If the team only ever handles one property's conversations, an admin can change its scope from the organisation to that property in the team's settings. The team then stops picking up conversations from anywhere else, and the notifications stop with it.
This is usually the right fix, because it keeps you in the team and keeps you covering the conversations you are meant to cover.
Step 3: Leave the team, if it genuinely serves several properties
Some teams are meant to be organisation-wide, for example a catch-all for guest messages that have not been routed to a property yet. If you do not need to cover that team, an admin can remove you from it.
Before you leave a team, check what it is for. If it is the fallback for unrouted guest conversations, leaving means you will no longer see or be notified about anything that lands there, including the occasional message from one of your own guests. Agree it with your account admin first.
Step 4: Or turn down the notification itself
If you want to stay in the team and simply hear about it less, change which notifications you receive. The one behind most of this is Conversation Assigned to Team, which notifies you every time a conversation is assigned to any team you belong to. See Inbox notifications for the full list.
What this does not do
Changing your own property access will not help. The conversation is reaching you through the team, not through your property assignments.
Only an admin can re-scope a team or remove you from one. Steps 2 and 3 need admin access; step 4 you can do yourself.
Re-scoping is not retrospective. It stops future conversations reaching the team. Anything already assigned stays where it is.
What to do next
If you run several properties, Managing teams across multiple properties explains how scope decides which team receives a conversation in the first place.
Getting help
Open Talk to Us in the left menu, or email support@bookboost.io. Include the name of the team, the property you work in, and an example of a conversation you were notified about.