Update profiles from a table

Export all, and Export on the selection bar, open the How to export window: Table, CSV, Table, Excel (.xlsx) or ARMANOS settings file (.json).

The table has exactly the columns an import understands: ID, Name, Group, Status, Tags, Notes, Proxy, Template and 2FA. The ID column is always there, the others can be unticked. Change the cells and import the file back: the rows update these same profiles, and no new ones appear.

The profile password and cookies never go into the table. Proxy passwords and 2FA keys go only with With proxy passwords and 2FA keys ticked; without it the 2FA cell is empty, the proxy has no password, and on the way back the passwords stay as they were. A 2FA key with 8 digits or a 60 second step goes out as a whole otpauth:// link, so after the way back the codes are the same.

Profiles shared with you by your team without the right to export, and profiles locked by a password, do not go into the table, and the window names them. There is no kernel column: a kernel is downloaded on each computer separately and changed in the profile window.

A column named ID, profileId, uuid or Profile ID is recognised by itself, and any other column gets this field in This column. Copy ID in the profile menu gives you the ID of a profile.

A row updates a profile only when the column holds the ID of a live profile from this list. An ID that is not here means a new row: a new profile is created with a new ID.

It changes the name, the group (a new one is created), the proxy (it goes into the library), the notes, the tags, the status, the ports, the 2FA key and the cookies. Tags are replaced by the list in the cell, and cookies are added to those already there.

An empty cell changes nothing: to keep a field as it is, leave the cell empty or remove the column. A proxy without a password that matches the current one by kind, host, port and login keeps the password.

Import does not change the system and the User-Agent of an existing profile: that would make it a different machine. A row whose system differs gets a note about it, and you change the system in the profile window.

A count stands above the preview: New profiles: 3 · Profiles to update: 2. Each row of the preview has a What happens column: New, Updates with the profile name and the fields that change, or Skipped. A skipped row is not counted, and neither is a row with a problem while Skip the rows that could not be read is ticked.

A field whose cell equals the profile is not named. A row where all of them are equal says Nothing to change in “Name”: it leaves the profile alone and is not counted either.

The choice Rows with a profile ID stands on Update that profile; Skip the row leaves those profiles as they are. The button says the same as the count, for example Create 3 and update 2.

1. 1

   Read the file or the pasted text

   The IDs are recognised in the preview, and nothing is changed yet.

2. 2

   Check the What happens column

   A row that would update the wrong profile shows here by name.

3. 3

   Press the button

   The result names how many were created and updated, and every row skipped because of its profile ID, with the reason.

The window skips a row and names the reason when the profile with this ID is in the recycle bin, is locked with a password or is one you cannot change. When one ID stands in two rows, the first row updates the profile, and the second names the row that does.

When the file has an ID column but none of its IDs belongs to a profile of this account (an export of another app), the window says so in one line, and every row becomes a new profile.

The profile ID is the seed of its fingerprint. If the ID from a table went into a new profile, one table imported by two people would give them two identical machines, and importing an export after a permanent delete would bring the erased machine back.

So the ID from a table only looks up a profile, and a new profile gets a new ID. A profile moves together with its machine through an archive or a profile transfer.