Being asked
When someone in support needs to look, a request appears here marked waiting on you, and it carries their reason in their own words — “Checking why the Tuesday post did not publish.” You are answering that specific request, not signing a standing permission. Two buttons, equal weight:- Allow for 30 minutes
- No thanks — which takes effect immediately and asks you nothing further.
What “read-only” means
While a look is live, support sees the product as you see it. They cannot change anything: no settings, no content, no publishing, no spending, no permissions. Nobody on our side can act as you. Every page viewed that way is recorded, so the look leaves a trail whether or not anything comes of it.While it is running
An allowed request turns into a panel at the top of the page saying support is viewing your account right now, with the minutes left on the clock and the reason they gave. Stop now ends it immediately. You do not have to explain, and you do not have to wait for the 30 minutes. If you do nothing, it ends on its own when the clock runs out.The record
Earlier requests lists what has happened before — when it was asked for, the reason given, and how it finished:
Times on that list are shown in UTC and labelled, because it is a record of when
permission was asked for rather than an entry in your own day.
It is your consent, not your account’s
Every person on the account has this page, and each answer is that person’s own. Nobody — not an admin, not the owner — gives it for you, and answering is not something a role grants or withholds.If the page cannot check
If we cannot look up your requests just now, the page says so plainly instead of telling you there are none. “We could not check” and “there is nothing” are different answers, and a privacy page should never confuse them. Reload in a moment.Related
- Your data and privacy — what is stored, who can see it, and how to get a copy.
- People and roles — who on your own account can see what.