Users, access and backups

Every XiroLink bridge runs on its own server with its own database and fixed IP. This page covers who can sign in, who can connect, how changes are recorded and how your data is backed up.

Users and roles

Manage users under Settings → Users. Add user asks for a username, email and role:

Role	Can do
Admin	Everything, including users and settings
Viewer	See everything, change nothing

Leave the password empty to email an invitation instead; it works for 72 hours. From each user's menu you can resend the invitation, email a reset link, disable or enable them, reset their two-factor sign-in, or delete them.

Two-factor sign-in

Require two-factor sign-in for viewers is on by default: viewers set up an authenticator app at their next sign-in. Admins can turn it on for themselves under Settings → My account, and you can exempt a single user where needed. People who open the bridge from the XiroLink portal use the portal's own two-factor sign-in.

Under Settings → General, Session length sets how long a sign-in lasts (24 hours by default), and Sign-in attempts per minute limits guessing from one IP address.

Who can connect

Takers accept connections only from their Allowed IPs. On top of that:

• Blocked IPs on the Security page cannot connect to any taker. Block an address by hand, permanently or for an hour, a day or a week, with a reason. Blocking closes its live connections at once. You cannot block your own address.
• Automatic blocks stop an address after 10 failed attempts within 5 minutes, such as wrong credentials or an IP not on the list, for 60 minutes. They are marked Auto.
• Unblock an address from the same list. It is then subject to each taker's allowed IPs again.

The Sessions tab on Takers shows every connection and rejected attempt for 90 days, with the client IP, how long it stayed and why it ended, such as Wrong credentials, IP not allowed or Heartbeat timeout. From there you can block an address, or allow it on that taker.

Audit log

The Audit log on the Security page records every change: who made it, from which IP, what changed and the value before and after. Passwords and secrets are shown as redacted. Search it, or filter by sign-ins, users, makers, takers, symbols, trading hours, settings or IP blocks.

Each maker, taker, symbol and profile also shows its own Change history, with a link to the full log.

Credentials

Maker and taker passwords, notification secrets, settings and two-factor keys are stored encrypted. They are never shown again after saving: type a new value to replace one.

Backups

Under Settings → Backup, turn on Automatic backups and point them at any S3-compatible storage:

Field	What to enter
Endpoint URL	Your storage provider's S3-compatible endpoint
Access key, Secret key	Credentials with write access to the bucket
Bucket, Region	Where backups go. Region can stay on auto for most providers.
Every (minutes)	How often to back up. Default 5.
Key prefix	A folder for the backups. Default bridge-backups/.

Test connection checks the details, and Back up now runs one straight away. Each backup is a snapshot of the bridge's database, and older log files are uploaded too. To restore from a backup, contact support.

Your server

Each bridge runs on its own server with its own database and a fixed IP that is never shared with another broker. A reserved IP, included in Enterprise or available as an add-on, stays the same even if the server is replaced. Enterprise plans can also choose the server's region.