Tej strony nie ma jeszcze w Twoim języku. Czytasz tekst angielski.
Knowledge base
Bookmarks for profiles
Three moves
Add puts the bookmarks on the bookmarks bar, and the bookmarks each profile already has stay.
Replace removes the bookmarks of each profile and puts the new ones. Clear only removes them.
Replace and Clear leave team bookmarks alone: they come back at the next launch.
Lines or a file
One bookmark per line: folder::name::address, name::address or just an address. Bare addresses can share a line, separated by spaces.
Import an HTML file takes the bookmarks file that Chrome or another browser exports. The folders from the file stay.
Only http and https addresses count. Other lines are skipped, and the result names them by number.
Open profiles
While a profile is open, its browser holds the bookmarks file. Such a profile gets the change at the next launch, and the result names it.
The same goes when the profile session on another computer is newer: the bookmarks land after it comes here.
Team bookmarks
The Team bookmarks card on the Engine screen holds a list that goes onto a profile at every launch in ARMANOS Browser.
For picks which profiles get it: All profiles, or the profiles of the groups you tick.
The built-in engine has no bookmarks bar, so it shows team bookmarks on the start page instead of quick links.
Export
Export bookmarks in the bookmarks window writes one HTML file per selected profile. Any browser opens such a file.
The Export bookmarks button in the team card writes the whole team list the same way, as one file.
What this does not do
- Without an account the team list lives on this computer and goes into the profiles opened here. A server you built yourself before the update does not keep team bookmarks: then the list also lives on this computer.
- The built-in engine has no bookmarks bar: the bookmarks are there when the profile opens in ARMANOS Browser.
- Up to 1000 lines at a time, an HTML file up to 16 MB, up to 500 team bookmarks.
- Password-closed profiles are skipped and named.
Where this is decided
The claims that carry the most weight, with the stand that checks each of them.
- Bookmarks in bulk: a closed profile is written, an open one gets the change queued until launch, a password-closed one is skipped and named, lines with mistakes are named by number
- apps/desktop/test/закладки-в-окне.js
- ARMANOS Browser reads the app file as its own: the bookmarks on the bar in the same order, the same checksum, and repeating the team list does not multiply them
- apps/desktop/test/закладки-живьём.js
- Replace and Clear leave team bookmarks alone; a queued change runs at launch after the session has arrived
- apps/desktop/test/закладки-в-файле.js
- The start page shows team bookmarks as text: a name with markup runs nothing
- apps/desktop/test/закладки-в-окне.js
- Signing in does not put bookmarks added before sign-in into team profiles: a member has them set aside, an owner moves them into the list only with the button and without repeats
- apps/desktop/test/закладки-команды-при-входе.js
Questions
- Do team bookmarks double at every launch?
- No. A team bookmark carries its own mark, and a launch puts the team list in place of the previous one, not next to it.
- What happens to bookmarks added in the browser itself?
- They stay. Add and team bookmarks leave them alone; only Replace and Clear remove them.
- Who changes team bookmarks?
- Without an account, you do. In the app with an account, the workspace owner and an admin do, and a member sees the list but does not change it.
- What happens to the bookmarks I added before signing in?
- They stay on this computer and do not go into team profiles by themselves. The workspace owner and an admin put them into the team list with Send my bookmarks to the team; a member gets them back after signing out.
Try it on your own profiles
The free plan gives two profiles, with no time limit and no card.