A business usually is not run by one person. Team is where you give a colleague access and choose what that access covers.

Adding someone

Go to Team, choose Add someone, and give their email address and a role.
They need a Paynecta login already. Adding them does not create one, and it does not give them a second password: the login they have works for every business they belong to.
They get an email telling them who added them, to which business, and what their role lets them do.

The four roles you start with

Every business is created with these. You can use them as they are.

Building your own role

When none of the four fits, build one. Team → Roles → New role, then tick the permissions it should carry, grouped by the part of Paynecta they apply to. A few that come up often:

KYC Officer

Gathers documents and submits verification, but cannot touch settlement.

Finance Officer

Sees where money settles and reconciles it, but cannot change the bank.

Auditor

Read-only across everything, changes nothing.
Grant only what the job needs. Anything unticked is refused by Paynecta itself, not merely hidden from view, so a narrow role is a real boundary.

The rules that will not bend

Not even by an administrator who can remove everyone else. Ownership is transferred deliberately, never taken.
It is not in the list when you add someone, and it cannot be assigned afterwards.
Deleting it would quietly take access away from the people holding it. Move them to another role first.
You can build as many of your own as you like alongside them.

Removing someone

Removing a member takes away their access to this business only. They keep their Paynecta login and any other business they belong to.