Client-owned accounts
The client retains primary ownership and invites Biancorp through the platform’s supported role system.
Client-owned accounts
Biancorp uses supported platform roles and attended remote sessions. The client keeps ownership, can see who has access, and does not need to hand over passwords for routine work.

Access model
Each system handles roles differently. The working rule is the same: give a named person the minimum access needed for the task, then review that access when the work changes.
The client retains primary ownership and invites Biancorp through the platform’s supported role system.
Passwords, authenticator secrets, backup codes, and one-time verification codes are not collected for routine management.
Major edits, access grants, removals, and remote-session work are tied to a person, purpose, and date.
Only the information needed to deliver, support, document, and secure the agreed service is requested.
Appointment-only remote desktop support
When a screen demonstration or hands-on support is the clearest option, Biancorp may use its ISL remote support client. The client launches the support application for the appointment, sees the active session, and can disconnect it.
See the complete session processGoogle Meet consultations
After the consultation request is reviewed, a free Google Meet may be offered when a conversation would help. If supported recording or transcription is enabled, the meeting interface and any applicable notice inform participants.
Access lifecycle
Need help sorting out access?
Share what applies, choose the closest working budget or planning range, and never submit passwords or verification codes. We will review the request and, if a meeting would help, coordinate a free Google Meet.