Getting access to Nextera products
Konten ini belum tersedia dalam bahasa Anda.
Nextera products are delivered as hosted web applications. Each product has its own address and its own user list — access to one does not imply access to another.
Where each product runs
Section titled “Where each product runs”| Product | Address |
|---|---|
| Nextera Bright | bright.nextera.id |
| Nextera Link | link.nextera.id |
| Nextera Flow | flow.nextera.id |
| Nextera Accord | accord.nextera.id |
| Nextera Guard | guard.nextera.id |
| Nextera Trace | trace.nextera.id |
Nextera Track and SunSystems engagements are delivered differently; your Nextera contact will confirm the address for your organisation.
These are production addresses for existing customers. If your organisation uses a dedicated environment, your address will differ — use the one in your onboarding pack rather than the table above.
What to have ready when requesting access
Section titled “What to have ready when requesting access”Whoever provisions accounts in your organisation will need all of this. Gathering it before you ask is the difference between an account today and an account next week:
- Full name and work email address. The email address is normally the username.
- Which product, and which environment if you have more than one.
- What the person needs to do, described as tasks rather than as a role name — “enter and review lease contracts for the Jakarta entities”, not “give them the finance role”. Role names differ between products.
- Their scope, if your configuration restricts users by entity, business unit, branch, portfolio or channel.
- Who approves it. Access to financial and audit systems is itself an ICoFR control at most organisations; expect an approver, and expect that approval to be evidenced.
- A start date, and an end date if the access is temporary — secondments, external auditors and implementation consultants should be time-bounded from the outset.
Leavers and movers
Section titled “Leavers and movers”Access reviews are one of the most commonly failed IT general controls. Two habits prevent almost all of it:
- Raise the removal request in the same workflow that handles the leaver, not afterwards.
- Treat an internal move as a removal plus a new request, not as an amendment. Accumulated access from previous roles is what creates segregation-of-duties conflicts.
If you use Nextera Guard, user access reviews are a natural fit for its control library and testing cycle.
Signing in and account management in the product
Section titled “Signing in and account management in the product”If you cannot sign in
Section titled “If you cannot sign in”Check the obvious three first — correct address for your organisation, correct email address, account not yet activated — then contact whoever administers the product in your organisation. If they cannot resolve it, see Support.