IT Management & Support (Outsourcing): coverage in São Leopoldo - RS

Onboarding and offboarding as a defined process

Onboarding usually works, because there is someone waiting to start work and pushing for it. Offboarding does not, because there is no one pushing — the person has left and nobody misses their access.

What fixes this is turning both ends into a routine with a fixed checklist. On the way in: which accounts to create, in which groups, with which permission profile, with which equipment, and a record that it was done. On the way out: which accounts to deactivate, which access to revoke, which equipment to collect, what to do with the person's files, and who inherits what they maintained.

The detail that makes the difference is tying the process to the business event. When the departure or the contract's end triggers the routine automatically, it happens; when it depends on someone remembering to tell IT, it happens sometimes.

Access by expiry date instead of by memory

For engagements with a known end — internships, grants, project contracts — it pays to create access with an expiry date from day one. That inverts the error pattern: instead of access lasting forever until someone removes it, it expires and gets renewed if it is still needed.

It is a small configuration change with a large effect in a high-turnover environment, and it solves at the source the orphaned-account problem that any initial survey finds in quantity.

Permissions by role, not by person

In an environment with heavy churn, granting permissions individually does not scale and produces a well-known effect: each new person receives access copied from someone similar, including the access that person should never have had in the first place. Privilege propagates by inheritance.

The alternative is to define profiles by role — what an intern in a given area accesses, what a researcher accesses, what administration accesses — and assign each person to a profile. Granting becomes a simple decision, so does revoking, and the question "who has access to this?" finally has an answer.

Documentation where people rotate

Missing documentation is one of the risks on record for the city, and in a high-turnover environment it costs more than anywhere else.

The reason is direct: when knowledge lives in people's heads and the people circulate, the knowledge walks out the door every cycle. The operation ends up periodically rediscovering the same things — how that system is configured, why that rule exists, where anything is.

Managed service keeps that record as a by-product of the operation, not as a separate project. Every change executed updates the documentation because it is the same process — and that is what lets the environment outlive the rotation of whoever was running it.

Remote-first operation and the prepared environment

Service is primarily remote, with response within 45 minutes, and physical presence is arranged when the problem requires someone at the site. In a technology and research environment, that format fits well, because the fleet is manageable and the client's team is usually technically capable of collaborating on verification.

The condition is the usual one: remote access configured before the incident, an up-to-date inventory, and documentation. In a high-turnover operation there is one extra item — the inventory of who has access to what needs to be as current as the inventory of equipment.

The sectors that drive demand in São Leopoldo

Services, industry, technology, and education make up the city's profile. Technology and education concentrate the turnover described above and the need to separate environments — development, research, lab, and administrative must not blur into one another.

Industry brings operational continuity and equipment with its own lifecycle. Services firms weigh heaviest on confidentiality and continuity of service.

How service is conducted

It starts with the survey: equipment, systems, sites, links, and — with special attention — the access inventory, which is where the initial survey usually finds the most things out of place.

Next come the preparation for the remote model, the definition of role-based profiles, the onboarding and offboarding routines tied to business events, and the living documentation record.

With that in place, the remote channel absorbs the day-to-day within 45 minutes, physical presence comes in scheduled for what is physical, and the periodic report includes an access review — the check that answers, every month, whether anyone still holds access they should not have.