Remote access sounds like a user-interface question:
“Can I get into Sage from somewhere else?”
But the quality of that experience is heavily influenced by what is happening underneath.
Where Sage Runs Matters
Sage 100 depends on the environment supporting it.
The location of the application, company data, user sessions, printers, reporting tools, integrations, and connected services can all influence how the remote workflow behaves.
Remote Users Still Need the Whole Workflow
Getting to the Sage menu is only the beginning.
Users may still need to:
- Email Paperless Office documents
- Run Crystal Reports
- Use Sage Intelligence
- Reach shared paths
- Run Visual Integrator jobs
- Access ODBC-connected tools
- Use scanners, warehouse tools, or other integrations
A remote-access design has to account for those workflows too.
Architecture Is Where IT and Sage Expertise Meet
The IT team understands the infrastructure platform.
We understand what Sage and its users are going to ask that platform to do.
A good remote environment is built where those two sets of requirements meet.
Sage's Own Materials Emphasize Remote Flexibility
Sage includes flexibility of remote access among the potential benefits of cloud deployment.
The important word is flexibility.
There is not one universal remote-work design for every Sage 100 client.
The architecture should follow the business.