Bu sayfa henüz sizin dilinizde yok. İngilizce metni okuyorsunuz.
Knowledge base
Install an extension inside a profile
The setting
Allow installing extensions inside profiles (ARMANOS Browser) stands on the Extensions screen and is on by default. It takes effect at the next launch of each profile.
With it off, a profile starts with only the extensions of the app, as before.
What the Extensions screen shows
Choose a profile in the toolbar of the Extensions screen. The block Installed inside profile lists each extension with its version and where it came from.
from the store
Installed with Add to Chrome.
your folder via developer mode
Loaded from a folder in the developer mode of the browser.
not installed by you: by the system
Put there by another program on this computer.
not installed by you: by a policy
Put there by a browser policy of this computer.
An extension you did not install
If a profile has an extension put there by the system or a policy, ARMANOS opens it with only its own extensions this time, and a notification names the extension.
At the first launch without the ban, a notification also names the extensions already lying in the profile that will now run.
Teams
The owner and admins see Forbid team members to install extensions inside profiles. It is stronger than the setting on the members’ computers.
The browser flag cannot say use, but do not install, so for members extensions installed inside earlier do not load either. Shared extensions for the team are installed on the Extensions screen.
On the built in engine
Extensions installed inside a profile work only in ARMANOS Browser. On the built in engine, open the extension page in the store inside the profile and choose Install this extension in the profile in the Profile menu of the app.
What this does not do
- It does not remove or turn off an extension installed inside: that is done in the profile itself.
- It does not promise that such an extension moves with the profile to another computer.
- It does not load extensions put there by the system or a policy.
Where this is decided
The claims that carry the most weight, with the stand that checks each of them.
- The census reads what is installed inside, keeps a path inside the profile, and a member under the team ban starts with the ban
- apps/desktop/test/расширения-профиля-перепись.js
- By default a profile starts without the ban, with the setting off it starts with it, a system extension brings it back, and the fingerprint is the same
- apps/desktop/test/расширения-из-профиля-живьём.js
- An extension from the Chrome Web Store installed in an open profile works at once and after the profile starts again, and the Extensions screen shows it as from the store; the profile history gets a line about it already after the first session of a new profile
- apps/desktop/test/расширение-из-магазина-живьём.js
- Only the owner and admins can set the team ban, and a line about it appears in History
- apps/server/test/запрет-расширений-внутри.js
- The store page item takes the extension number from the address only
- apps/desktop/test/расширение-со-страницы-магазина.js
Questions
- Does a site see that the profile has my extension?
- Only as much as the extension shows itself. The fingerprint of a profile is the same with the setting on and off.
- Where does the history record it?
- After the profile closes, its history gets a line: an extension was installed inside the profile, with its name and where it came from (for example, from the store). This also holds after the first session of a new profile. An extension removed inside the profile gets a line about the removal.
Try it on your own profiles
The free plan gives two profiles, with no time limit and no card.