An operations or vendor portal needs three layers of access control: authentication (who the user is, ideally through the organisation's single sign-on plus multi-factor authentication), authorisation (a role matrix that limits what each role can see and do, scoped to specific properties or vendors), and accountability (an audit log of every sensitive action). Define all three in the requirement specification before any screen is designed.
This reference is written by Singapore-based AV and IPTV integrator Prestige Solutions for property managers, operations managers and IT teams specifying a custom software management system such as a vendor portal, maintenance ticketing tool or approval dashboard. It sets out the role matrix, sign-on options, session rules and audit fields that should be written into the requirements. Values given are planning defaults as of 2026 and should be confirmed against the organisation's own IT security policy.
Most failures come from permissions that were never designed, not from broken passwords. A portal starts with two roles, "admin" and "user", and every new need is solved by making more people admin. Within a year, external contractors can see every property's tickets, former staff accounts still work, and nobody can say who approved a purchase order. The OWASP Top 10 (2021 edition) lists Broken Access Control as category A01, the most common serious weakness found in web applications.
Three design decisions prevent most of this:
The role matrix is the single most useful document in the specification: a table of roles against actions, with the scope each role applies to. It lets the property team, the vendor and the developer agree on behaviour before code is written, and it becomes the test plan at acceptance.
| Action | Portal Admin | Property Manager | Ops Supervisor | Vendor Coordinator | Vendor Technician | Auditor (read-only) |
|---|---|---|---|---|---|---|
| Create work order | Yes | Own properties | Own property | No | No | No |
| View work orders | All | Own properties | Own property | Assigned to own company | Assigned to self | All |
| Update job status and upload photos | Yes | Yes | Yes | Own company jobs | Own jobs | No |
| Approve quotation | No | Up to approval limit | No | No | No | No |
| Invite or disable vendor users | Yes | No | No | Own company only | No | No |
| Change roles and scopes | Yes | No | No | No | No | No |
| Export reports | Yes | Own properties | No | No | No | Yes |
| View audit log | Yes | No | No | No | No | Yes |
Two rules keep the matrix healthy. First, the Portal Admin role manages users and configuration but does not approve spending, so no single account can both create a vendor and pay it. Second, aim for fewer than about 10 roles; when a request for a new role arrives, check whether a scope on an existing role solves it.
Approval limits are data, not roles. Store the limit per user or per role and property (for example, a value up to which a Property Manager can approve, with anything above routed to the next approver), and let the approval workflow read it. Creating roles such as "Manager 5k" and "Manager 20k" multiplies the matrix and is hard to audit. The approval routing itself is covered in the approval and SLA records case.

Use the organisation's identity provider for internal staff, and a managed account with multi-factor authentication for external vendors. Internal users should sign in through single sign-on (SSO) so that disabling their corporate account also removes portal access on the day they leave. Vendors rarely have an identity provider the property team can trust, so they need portal accounts with their own controls.
| Method | Standard | Best fit | Points to specify |
|---|---|---|---|
| OpenID Connect (OIDC) | Identity layer on OAuth 2.0 (RFC 6749) | Modern web and mobile apps; Microsoft Entra ID, Google Workspace, Okta | Authorisation code flow with PKCE (RFC 7636); group claims mapped to portal roles |
| SAML 2.0 | OASIS standard, XML assertions | Enterprises with existing SAML-based SSO | Signed assertions; certificate rollover procedure; attribute mapping |
| Local accounts with MFA | Password plus TOTP (RFC 6238) or passkey (WebAuthn) | External vendors and contractors | Password hashing with Argon2id or bcrypt; lockout and reset rules |
| Magic link or one-time code by email | No formal standard | Occasional, low-risk external users | Short link expiry; limited to view and update of own jobs |
When SSO is used, decide where roles live. Mapping identity provider groups to portal roles (for example, a group named for property managers mapped to the Property Manager role) keeps joiners and leavers in one place. Scopes such as which property a manager covers are usually kept in the portal, because identity providers rarely hold that detail. Where the organisation supports SCIM 2.0 (RFC 7643 and 7644), user provisioning and deactivation can be automated as well.
Require MFA for every role that can approve, export or administer, and for all external accounts. Read-only internal users signing in through SSO inherit the identity provider's MFA policy. The table below gives planning defaults as of 2026; the organisation's security policy overrides them where stricter.
| Setting | Planning default | Note |
|---|---|---|
| MFA methods | Authenticator app (TOTP, 6 digits, 30-second step) or passkey | SMS codes only as a fallback |
| Idle session timeout | 15 to 30 minutes for admin and approver roles; longer for technicians on mobile | Mobile field apps often use a shorter-lived access token with a refresh token |
| Absolute session lifetime | 8 to 12 hours (one working shift) | Forces daily re-authentication |
| Failed login handling | Progressive delay or temporary lock after about 5 to 10 failures | Avoid permanent lockout that vendors can trigger against each other |
| Password rule for local accounts | Minimum 12 characters, checked against known breached passwords | No forced periodic changes unless compromise is suspected |
| Step-up authentication | Re-prompt MFA before approving above a threshold or changing roles | Protects the highest-impact actions |
Shared logins are the one practice to rule out completely. A front-desk tablet or a contractor team sharing one account makes the audit log meaningless. Where a shared device is unavoidable, give each person a quick personal sign-in on it, such as a PIN tied to their own account.

Delegate vendor user management to a Vendor Coordinator at each vendor company, but keep the property team in control of which companies and scopes exist. This avoids the portal admin becoming a bottleneck while making sure no vendor can grant itself access to new properties.
The audit log should answer who did what, to which record, when and from where, for every action that changes data, permissions or money. It is separate from application error logs, it cannot be edited by any portal role, and it is kept for the period the organisation's records policy sets.
| Field | Example content |
|---|---|
| Timestamp | UTC time with time zone offset recorded (Singapore is UTC+8) |
| Actor | User ID, role and scope at the time of the action |
| Action | Approve quotation, change role, export report, sign in, failed sign in |
| Target | Record type and ID, such as work order or user account |
| Before and after | Changed fields only, for example status or approval amount |
| Source | IP address, device or app version, SSO or local sign-in |
| Result | Success or denied, with reason for denied requests |
Denied requests are worth logging as carefully as successful ones; a burst of denied actions is often the first sign of a misconfigured role or a misused account. Where audit data is exported to other systems, the integration and data ownership note covers who owns those copies.
Turn the role matrix into test cases and run them against the API, not only the screens. Each cell of the matrix becomes at least one test: sign in as the role, attempt the action inside and outside its scope, and confirm the expected result.
Record each result against the matrix cell and keep it with the handover documents, so that later changes can be regression-tested against the same table.

Other operations software, AV and hotel systems delivered by the same team are listed on the Prestige Solutions home page.
For internal staff, connect to the organisation's existing identity provider rather than building a login. For external vendor accounts, a proven authentication library or managed identity service is safer than custom code, because password storage, MFA enrolment and account recovery are easy to get subtly wrong.
Yes, but keep it rare and visible. A user can be a Property Manager at one property and an Ops Supervisor at another, since roles are scoped. Avoid combining roles that are meant to check each other, such as Portal Admin and an approving role, on the same account.
Use a documented break-glass account with a long password and MFA, held under the control of two people, with every use alerted and reviewed afterwards. This is better than leaving permanent elevated access on everyday accounts in case it is needed at night.
Contact Prestige Solutions to review your site drawings and current operating pattern. Call +65 8010 2337 or +65 9825 8218, message us on WhatsApp (+65 8010 2337), or email sales@prestigesolutions.com.sg. You can also browse the full product range before the site walk.
Explore our full product range or speak with our technical team for a tailored consultation.