Adding a team member

There are two ways to add someone, and the difference matters:

• Invite member – for a person who already has a Fiberax account, or who will create one. You enter their email and name; they receive an invitation with a link, sign in (or register), and confirm. They keep their own password – you never see it.
• Add member – for a person who has no Fiberax account. You fill in their details and set their password yourself. The member is active immediately, no confirmation needed.

If the person already has a Fiberax account, “Add member” will not work – an account cannot be created twice for the same email address. Use “Invite member” instead. The form tells you this if it happens.

When adding someone yourself, leave Email them their sign-in details switched on – otherwise we will not contact the person at all, and you have to pass the login details on yourself.

Details and permissions live on one page and are saved together: you fill in who the member is and what they can access, then save once. To change a member later, open Edit member from the team list – the same single page.

Accepting an invitation

The invitation email contains a link. When the invited person opens it:

• If they already have a Fiberax account – they sign in and immediately see an “invites you to their account” screen with Accept / Reject. One click and it is done.
• If they do not have an account yet – they click Sign up, register, and land on the same Accept / Reject screen.

Until the person clicks Accept, the invitation stays Pending on your Team page. A stuck Pending almost always means the person has not finished signing in or registering through the link.

Important: how a member reaches your services

A team member signs in to their own account. Your services are not mixed into it – they have to switch across.

To do that, the member opens the user menu in the top right corner and picks Switch customer account, then selects your account. From that moment they see your services, with the permissions you granted. The same menu takes them back to their own account.

This is the single most common source of confusion: a new member signs in, sees an empty portal and concludes the access does not work. It does – they just have not switched yet.

Permissions

Permissions are set in two layers: an access level for the whole account, and a role per project.

Access level

Three cards at the top of the permissions section:

• Full access – everything: all projects and services, billing, support and account settings. Includes services you create later.
• Custom – you choose a role for each project and pick the account permissions yourself. This is the usual choice.
• View only – read access everywhere: the member sees services, billing and tickets, but cannot change anything.

Role per project

With Custom, each of your projects and services gets its own role:

• No access – the member does not see this service at all.
• Viewer – read-only: sees the service and its charges.
• Operator – day-to-day work: power on and off, the browser console, backups and snapshots, restoring from a backup, mounting images, networks, IP addresses and the firewall.
• Admin – everything on this service, including reinstalling the operating system, changing resources, renaming, SSH keys, resetting the server password, and cancelling the service.

A role is a ready-made set of permissions – you do not have to assemble it from checkboxes. If you need something in between, click Customize on that row and tick individual permissions; the role then shows as “Custom”.

“Let a colleague run the servers in this project, but not reinstall them” is exactly Operator.

Account permissions

Below the projects are permissions that apply to the account as a whole, independent of individual services:

• Billing – invoices, payments and orders: view and pay invoices, place new orders, see the balance, add funds, see prices, receive billing emails.
• Support – tickets: open, view, close, receive notifications, see the whole organisation’s tickets, or be restricted to certain departments.
• Account management – contacts, emails, service groups, the affiliate section, the product catalogue.
• Sensitive permissions – these change who has access or let the member act as the account owner: editing card details, changing the main profile, allowed IP addresses, SSH keys, contacts, and Manage Teams.

Manage Teams lets the member invite other people into your account. Grant it only to those you would trust with that.

Copying permissions from another member

If a new member should have the same access as an existing one, use Copy permissions from another member at the top of the permissions section. It fills the whole set with theirs; review it and save.

The rest of the Team page

• Team name – a label for your team. Members see it when they switch into your account, which helps when someone works with several companies.
• Billing Contact – whose details are used for invoices and payments. By default the main profile is used.
• Log in as this contact – opens the portal as that member, so you can see exactly what they see. Useful when checking permissions.
• Delete – removes the member’s access to your account. Their own account is not affected.