What suXus configures
Request and naming rules, ownership, classification, periodic reviews, expiry dates, archiving and controlled deletion. Checks and reminders can be automated where the technology supports them.
Approach
suXus starts with existing workspaces, roles, retention needs and decision-making arrangements. Criteria are then defined for creation, use, review, archiving and deletion. Technical configuration and reporting are first validated for a defined group before wider use is considered.
Conditions and limitations
Automation can remind owners and execute established rules, but does not independently determine which information must legally be retained or deleted. Available features depend on Microsoft 365 configuration and licences. Exceptions, missing owners and conflicting retention needs require documented customer decisions.
Links with access and management
Permissions and security identifies who has access and where follow-up is needed. Microsoft 365 management incorporates approved changes, documentation and periodic activities into technical management.
Responsibilities
Responsibilities
suXus translates established policies into technical configuration and reporting. The customer retains responsibility for legal retention duties, classification, risk appetite and deletion decisions. Legal or compliance interpretation falls outside the technical service unless agreed separately.
Outcomes
Outcomes
An established process, technical configuration, exception register and reporting that allow the organisation to demonstrate that reviews take place and actions are followed up.
Technology
Technology used in these services
- Microsoft 365
- Microsoft Teams
- SharePoint