The walkthrough uses illustrative data to explain the workflow. It is not a customer account or a statement of available funds. Feature names match the current ROAMLINX portal.
Your team, organised
Roles and purchase limits belong to people, not shared passwords.
One trip. Clear recipients.
- Choose coverage, data and validity
- Select active team members
- Review the total and purchase result
The traveller installs their own eSIM after the order is fulfilled.
Purchases you can find again
Filter by employee and date. Keep expense data separate from invoice documents.
Employees: give access to the right person
An administrator invites an employee by email, selects the role and chooses the invitation language. The recipient uses an account with the same email address and verifies it. Check that membership is active before purchasing: sending an invitation is not the same as granting immediate spending access.
The employee list supports search, role and status filters, and monthly purchase limits. Employees can lower their own limit further, but cannot override the administrator’s restriction. Treat blocking membership and stopping any active services as separate decisions.
| Role | Typical responsibilities | Access boundary |
|---|---|---|
| Owner | Keeps administrative access to the organisation and manages the team. | The owner is not an ordinary employee membership that another member can simply block. |
| Administrator | Invites people, sets limits, orders packages and reviews company expenses and documents. | The management view does not reveal employees’ private eSIM installation codes. |
| Employee | Uses their own eSIMs and makes authorised purchases within the available limit. | Has no access to company administration or other employees’ private records. |
Order: buy for the people who are travelling
Select a package and recipients from the organisation’s active members. Check the quantity, currency, package terms and total before confirming. For a group trip, a final traveller list is more reliable than repeatedly buying spare packages without confirmed recipients.
A bulk order can have mixed results. One person might have no remaining budget or an inactive membership while other purchases succeed. Review every line rather than assuming one error means no orders were created. Use the order list to establish the actual outcome before buying again.
Services: understand the eSIM’s state
Administrators see services linked to the organisation, their recipients and available status information. Employees open their own eSIMs in their accounts to access installation details. Treat the QR code and activation information as credentials, rather than posting them in a company-wide chat.
Ready to install, installed, depleted and expired describe different states. The installation deadline may also differ from the end of an activated package’s validity. If the supplier has not supplied a reliable usage observation, missing data does not mean that nothing has been used.
Available actions depend on the service. The portal may offer suspension, resumption or cancellation of an eligible eSIM. Review the amount and conditions before cancellation. A deferred-payment purchase requires a separate accounting decision; it does not automatically turn credit into prepaid funds.
Expenses and Invoices answer different questions
Expenses show what was purchased, who received it and when. Filter by employee and date range, then export a CSV for internal reporting or matching purchases to trips.
Invoices contains issued documents and available PDF downloads. An expense export does not replace an invoice, and a filtered purchase total need not match a single billing period. If a correction is needed, quote the document and order numbers rather than changing an accounting amount in a spreadsheet.
The portal makes records available, but does not claim automatic integration with every finance system. Check your import process and required fields before making CSV export part of a regular accounting workflow.
Account: funds and agreed payment terms
This view shows the organisation’s balance and payment arrangement: prepaid funds or an agreed payment term. For prepaid purchases, arrange sufficient funds before employees need to order. Contact the team for the correct funding instructions.
A company balance, an employee’s monthly limit and a company credit ceiling are different controls. A higher employee limit neither adds funds nor increases agreed credit. Available company funds also do not remove restrictions assigned to an individual. Keeping those controls separate helps enforce a consistent purchasing policy.
A useful first session in the portal
Check the organisation name and currency. Invite one pilot traveller, confirm active membership and set a limited pilot budget. Then select a package for an actual trip rather than buying a product only to populate the interface.
Review the process from the traveller’s perspective too: finding the order, reading installation conditions and confirming the right device. Finally return to Expenses and check the recipient and purchase record. This catches organisational mistakes before a whole group leaves.
Questions before you decide
Why can an employee not see company administration?
The administrator console is for active owners and administrators. Employees manage their own eSIMs and available business purchases in their personal account interface.
Can a company administrator see a personal purchase?
Organisation views concern purchases and services linked to that company. Personal purchases are separate. Always check the selected purchasing channel before confirmation.
Is usage information a live meter?
Do not treat it as one. It depends on supplier updates, and an unavailable observation is shown as missing information.
Does the portal include ERP integration or SSO?
These are not advertised as standard features. Include such requirements in your enquiry so that feasibility and scope can be confirmed before rollout.