The cited material does not establish that the add-on needs its own login, workspace, or data store. It establishes narrower points: connected-app permissions determine when approval is requested before information is read or an action is taken, and those permissions do not themselves grant new access. A permission prompt alone therefore does not answer the separate-login, workspace, or storage questions.
What the permission rule tells you
A connected-app permission setting answers when approval should be requested. It does not, by itself, establish:
- whether the add-on requires a distinct sign-in;
- whether it uses an existing workspace or requires a separate one;
- whether information is kept in an independent data store.
The distinction matters because access approval describes a control over reading or action, not the add-on’s account structure, workspace boundaries, or storage arrangement.
How to check each requirement
Login: Review the setup instructions for a separate sign-in step or a requirement to create an independent account. If the instructions do not say, the login requirement remains unconfirmed.
Workspace: Look for an explicit statement about whether the add-on operates within the existing workspace or needs a new, isolated workspace. The cited material does not specify this.
Data store: Check the documentation for a separate storage location, independent repository, or other stated data-handling arrangement. The cited material does not specify this either.
What still needs confirmation
Before deciding that the add-on fits an existing setup, confirm each point through the add-on’s own documentation or the responsible administrator. The available source supports the permission-timing and no-new-access points only. It does not show that a separate login, workspace, or data store is present, but it also does not show that any of them is absent. An unanswered requirement should remain an open question rather than being inferred from the permission settings.