System Administrator: your first day

What you do

As a System Administrator, you manage the entire Usystems instance: user accounts, permissions, data integrity, security, and operational settings. You are the bridge between the organization's IT needs and the teams using Usystems. Your work ensures the right people have the right access, the system stays secure, and data is reliable.

Why this matters

A well-configured system runs smoothly and protects sensitive business data. Misconfigured permissions expose financial records to the wrong people. Missing backups or security policies create compliance risk. Over-permissioning leads to accidental data corruption. The administrator role is critical: your decisions shape how safely and efficiently the whole organization operates.

How it works in Usystems

Usystems administration is built around key areas:

• Users & Groups: Create accounts, assign roles, and manage access.
• Permissions & Roles: Define what each role can do (view invoices, edit accounts, run reports, etc.).
• Settings: Configure system defaults, organization info, accounting rules, and localization.
• Data & Backup: Monitor data integrity, export records for compliance, and manage recovery.
• Security: enforce password policies, manage API tokens, monitor login activity, and apply security patches.
• Audit trails: Review who did what and when, for compliance and troubleshooting.

All of this is centralized in the Settings or Administration area of Usystems.

Where you start

On your first day, you'll likely:

1. Review the user roster — see who has access and what permissions they have.
2. Verify the organization setup — confirm that the company name, financial year, chart of accounts, and accounting policies are correct.
3. Set up user roles (if not already done) — define roles like "Accountant", "Sales Manager", "Warehouse Staff" and assign appropriate permissions.
4. Check active integrations — see if the system is connected to banks, payment gateways, or other services; verify credentials are current.
5. Review security settings — ensure password policies, two-factor authentication (if supported), and session timeouts are appropriate for your organization.
6. Test user access — log in as a typical user (accountant, sales staff) and verify they see only the data and menus they should.

Key concepts to know

• User: A person with a login account and a password.
• Role: A bundle of permissions (e.g., "Accountant" can view all invoices and journals, but not delete documents).
• Permission: A specific action (e.g., "create invoices", "view reports", "manage users").
• صلاحیت‌ها (Permissions) in Dari: the system's term for role-based access control.
• Audit trail: A log of who changed what and when.

Next, read System Administrator: daily workflow to learn the day-to-day tasks you'll handle.