Background

Most operators and agents will use the server in their geographic region. There is nothing that restricts agents to using any particular server, agents are free to use whichever they want. Sometimes agents will need to use different servers in different contexts. This document lists some considerations for those who change from server-to-server over time.

Each server is a data island. Data is not shared between them. (*)

A team created on one server is only visible on that server. You cannot use a team on one server to control access to an operation on a different server. (There is a work-around using enl.rocks, linking a team on each server to a single rocks community will create sync'd teams across servers).

An op created on one server is only visible on that server. If you change servers, you can't just upload an op already on a different server to the new server. You'll need to duplicate the op in Wasabee-IITC and upload the copy to the new server. Any changes made to one of the copies will not be visible to the other.

Agents who have only logged into one server might not be known to the other servers

If you use multiple servers, do not assume that other agents use the same set of servers you do. If you cannot add an agent to your team, make sure they've logged into the server in question at least once (better yet, use team join links to add agents to your team).

There are 3rd-party/private servers

In addition to the three "official" servers, there is a "usually active" test server and a "sometimes active" development server. There are also servers not run by the Wasabee team. For special events, additional servers can be activated.

(*) Some data is actually shared between some servers

Wasabee servers can be federated with limited data sharing. The "official" regional servers are federated this way. The data shared is: community verification, intel name, agent firebase tokens, agent location. Community verification and intel name are shared since these are means of ensuring that only ENL agents use the servers. Firebase tokens are shared since these are used for real-time notification, an agent's token might change while using one server, if the other servers were not updated with the new token, notifications from the other servers would fail. Agent location is share between servers as a convenience to operators who are working multiple ops on different servers--all the usual privacy considerations are in effect (no historical data is saved, only team-members with whom the location is shared can see it, etc).