User provisioning and role assignment
Solutions · Administrators & Netsuite Teams
Property management that lives in your account
RIOO runs inside your NetSuite environment. You manage access, workflows and configuration with concepts you already know, and there's no second database to secure or reconcile. Confirmadministrators as a target persona
Admin · roles & scriptsNetSuite roles
- RIOO Property ManagerCustom roleAllowed
- RIOO LeasingCustom roleAllowed
- Scheduled scriptsBilling runAllowed
- Sandbox refreshPendingRestricted
09:41Bill VB-2207 approved · M. Chen09:44Posted to GL · system
The admin's real questions
NetSuite teams evaluating property software ask practical questions. Where does the data live? How are permissions handled? What happens at each NetSuite release? What integrations will we be supporting? Who fixes what when something breaks? These questions decide total cost of ownership far more than any feature list.
How RIOO helps
Data in your NetSuite account. Core property, unit, tenant and lease records live in NetSuite with your financial records. You aren't relying on an external vendor database for those records.
Roles and permissions. Role-based access determines which properties, units and data each user sees. Confirmhow RIOO roles map to NetSuite roles and custom permissions
Configurable workflows. Approval chains, routing and backups configured at property or community level, with a full activity log.
Integrations at the edges. Payments, messaging, e-signature, CRM, listings and utility billing connect around the core.
Release compatibility. NetSuite ships two major releases a year. RIOO maintains its application against supported releases. You should still validate your own critical workflows and configurations. ConfirmRIOO's release testing commitment and customer validation guidance
Why native matters →Workflows & customization →Integrations →
How it works
How implementation looks from your side
- 01
Architecture review
of your account, edition (including OneWorld) and add-ons such as Fixed Asset Management.
- 02
Configuration
of RIOO records, roles and workflows in your environment.
- 03
Data migration
of properties, units, tenants and leases.
- 04
Integration setup
for payment, messaging and document services.
- 05
In detail
Key areas you'll own
Property-level access scoping
Workflow configuration and changes
Integration credentials and monitoring
Saved searches and reports
Sandbox testing before releases
In detail
Governance that scales
As portfolios grow, admin work shifts from setup to governance:
RIOO's role-based access and workflow audit trail support each of these, using administration concepts your team already knows.
Access reviews
periodic checks that users still need the properties and roles they have.
Change control
documented approval for workflow and configuration changes.
Segregation of duties
ensuring requesters, approvers and payers are different people where required.
Onboarding and offboarding
quick, consistent provisioning as staff join and leave sites.
In detail
The administrator's toolkit on RIOO records
Because RIOO records are NetSuite records, standard SuiteCloud tools apply to them. These are the tools administrators use most. Confirmany limits on customising RIOO records
Saved searches
Build lists and alerts on leases, charges, work orders and renewals, such as leases expiring in 90 days without an offer.
01
SuiteAnalytics workbooks
Pivot and chart property data for finance and operations without exporting to spreadsheets.
02
CSV import
Load units, tenants or price changes in bulk during migration or acquisitions, with sandbox testing first.
03
Workflows
Configure approvals and routing for property transactions alongside your existing NetSuite workflows.
04
Custom fields
Capture portfolio-specific attributes, such as a lender reference on each property, within governance rules.
05
System notes
Review change history on any record when investigating an issue.
06
Explore by topic
Administrator priorities across the first year
First 90 days
Focus on stability. Watch for permission gaps that block site staff, tune saved searches and dashboards, and keep a log of change requests rather than acting on every one immediately. Run the first access review at the end of the period.
Months four to nine
Shift to improvement. Batch change requests into planned releases, retire workarounds that appeared during go-live, and run the first NetSuite release cycle with the property test script. Document each workflow and its owner.
Months ten to twelve
Prepare for growth. Plan how acquisitions, new entities or new property types will be onboarded, review integration monitoring, and agree a governance calendar of access reviews, release tests and workflow reviews for the year ahead.
What does a NetSuite administrator do on a RIOO rollout?
A NetSuite administrator on a RIOO rollout owns the account-level decisions that make property workflows safe: role design, property-level access, workflow configuration, integration credentials, sandbox testing and release readiness. RIOO's implementation team configures the application, while the administrator ensures it fits the account's existing structure, controls and other customisations.
The administrator's job changes shape after go-live. During implementation it is mostly design and testing. Once property teams are live, it becomes governance: provisioning site staff as they join and leave, reviewing access, managing change requests from operations and finance, and running the twice-yearly NetSuite release routine with property workflows in scope.
Compare
How should NetSuite roles be designed for property teams?
NetSuite roles for property teams should follow job functions, not individuals, and restrict each role to the subsidiaries and properties a person manages. A typical RIOO design has separate roles for site managers, leasing agents, maintenance staff, property accountants, AP clerks and controllers, each with only the permissions its tasks require. Confirmdelivered role templates
| Role | Typical access | Key restriction |
|---|---|---|
| Community or property manager | Leases, residents, requests, dashboards for own properties | Cannot post journals or release payments |
| Leasing agent | Prospects, applications, lease drafts | Cannot approve concessions above policy |
| Maintenance technician | Assigned work orders on mobile | No financial data beyond job costs |
| Property accountant | Charges, receipts, bills, reconciliations | Cannot change vendor bank details |
| AP clerk | Vendor bills and exceptions | Cannot approve own entries |
| Controller | Full finance, period close | Not a system administrator |
How it works
What happens to RIOO at each NetSuite release?
At each NetSuite release, RIOO is maintained against the new version, and your administrator validates critical property workflows in the release preview or sandbox before production upgrades. NetSuite ships two major releases a year, so building the property test script once and reusing it each cycle keeps the effort predictable.
- 01
Calendar
Note your account's release preview and upgrade dates as soon as Oracle publishes them.
- 02
Read
Review NetSuite release notes and RIOO's compatibility communication. ConfirmRIOO release notice timing
- 03
Refresh
Make sure the release preview or sandbox has recent data.
- 04
Test
Run the property script: new lease, rent run, payment, vendor bill match, work order, month-end report.
- 05
Check integrations
Confirm payments, messaging and e-signature still respond.
- 06
Sign off
Record results and approvals before the production upgrade.
Who is RIOO NOT a good fit for, from an administrator's view?
RIOO is not a good fit for organisations with no one able to administer NetSuite, internally or through a partner. Because RIOO lives in your account, someone must own roles, releases and change control; without that ownership, permissions drift and release testing gets skipped, which puts property operations at risk.
It is also a poor fit where the NetSuite account is already heavily customised around a different property tool or a legacy rent ledger. Those accounts need cleanup and a clear decision about which records RIOO will own before implementation, otherwise duplicate logic will compete for the same transactions.
What changes
What changes when administrators & NetSuite teams runs on NetSuite?
When administrators & NetSuite teams runs on NetSuite through RIOO, operational work and accounting stop being two separate jobs. Transactions post to the general ledger as they happen, reports use the same records as daily work, and controls come from NetSuite roles and approvals. The changes below are the ones teams usually notice first.
- One platform to secure and govern
- No sync jobsbetween a property system and the ERP for core records.
- Familiar administrationin NetSuite.
- Clear responsibilitiesat each release.
How it works
Release readiness, in practice
NetSuite's two major releases a year are routine for experienced admin teams, but property workflows add stakes. A practical release routine:
- 01
Review release notes
for changes affecting records, workflows or integrations you use.
- 02
Check RIOO's release communication
for compatibility notes. Confirmcommunication process
- 03
Test critical workflows
in your release preview or sandbox: lease to ledger, rent posting, AP matching and month-end reports.
- 04
Validate integrations
such as payments, messaging and e-signature.
- 05
Confirm role access
still behaves as expected.
- 06
Sign off
with finance and operations owners.
Talk to a specialist
See administrators & NetSuite teams on your own portfolio.
You manage access, workflows and configuration with concepts you already know, and there's no second database to secure or reconcile.
Is RIOO a SuiteApp?
RIOO is property management software built natively on NetSuite, which means its records, workflows and transactions live inside your NetSuite account rather than in an external database synced to it. Ask RIOO during evaluation for its current packaging and installation method, and any Oracle program status. Confirmapproved wording on SuiteApp/Built for NetSuite status; do not claim a BFN badge unless verified
Is there a separate RIOO database?
No separate database holds core property and financial records. Properties, units, tenants, leases, charges and payments live in NetSuite alongside your other financial data. Some supporting components, such as resident portals or connected services, may hold limited data outside NetSuite, which RIOO can map for your review. Confirmany external components (e.g. portals) and where their data resides
Who handles release compatibility?
RIOO maintains its application against supported NetSuite releases, and your team validates critical workflows and your own customisations in the release preview or sandbox. A reusable test script covering lease creation, rent runs, payments, vendor bill matching and month-end reports keeps that validation quick and repeatable each time NetSuite upgrades.
Which NetSuite setup do we need?
The setup depends on your structure. Multi-entity consolidation across property-owning companies needs NetSuite OneWorld, and automated depreciation of buildings and park-owned homes needs Fixed Asset Management. Single-entity portfolios may need less. RIOO reviews your account during the architecture stage and confirms what your structure requires.
Can we use our existing NetSuite sandbox for RIOO testing?
Yes, where your licence includes a sandbox account. RIOO configuration and test data can be deployed there first, so property workflows are tested alongside your existing customisations before production. Refresh the sandbox before major tests so results reflect current data, and keep integration credentials pointed at test endpoints. Confirmsandbox deployment process
How do we give a new site manager access quickly?
Assign the standard property manager role and restrict it to that person's properties or subsidiaries. Because access follows roles rather than individual permissions, a new manager can be productive on day one, and moving them to another site later is a change of restriction rather than a rebuild. Remove access on the day someone leaves.
Related
Related to administrators & NetSuite teams
Bring your toughest architecture questions.
