Team rules

Joining the team means signing the collaboration agreement, the confidentiality agreement, the code of conduct and the data protection commitment. These rules explain how they apply day to day.

1. Conduct

• Treat users and teammates with respect, in public and in private. No harassment, discrimination or humiliation.
• Follow the Community guidelines yourself: as staff you're held to a higher standard.
• Be fair. Decide the same way for a friend as for a stranger, and step aside when you have a conflict of interest.

2. Confidentiality and data

• Everything you see because of your position is confidential: user data, reports, cases, internal conversations, plans and code.
• Look at personal data only when a task needs it. Every access is logged and reviewed.
• No screenshots, exports or forwarding of internal information outside the team's tools, unless your task requires it.
• Report any leak or suspicious access to Security immediately.

3. Using your permissions

• Your permissions exist for your job. Never use them for personal reasons, favours or revenge.
• Every moderation action, correction and decision needs a reason, written where the tool asks for it.
• Never share your account, sessions, codes or access with anyone — not even another staff member.
• Two-step verification is required for the Control Center and recommended for every staff account.

4. Shifts, breaks and attendance

• Clock in when you start working and clock out when you finish. Clocking time you didn't work is a serious breach.
• Log your breaks (meal, short or personal) so the team knows who's available.
• Forgot to clock out? Tell your manager: they'll correct it with a reason. Don't correct your own shifts.
• Request leave in advance from Time off. If something unexpected happens, let your manager know as soon as you can.
• Weekly hours are a guide agreed with your manager; your wellbeing comes first. Tell People & Recruiting if the workload is too much.

5. Tasks and proof

• Do your daily routine and the recurring tasks of your position. Missed tasks are recorded.
• Finish tasks with honest proof: a written report and, when there are, screenshots, documents or links. Fake proof is a serious breach.
• If you can't finish something, say so early and explain why.

6. Support and moderation standards

• Answer users kindly, clearly and in their language when you can. Never promise what you can't deliver.
• Mark yourself Away or Offline in the support console when you can't take conversations.
• Escalate what's beyond your tier or department instead of guessing, with an internal note explaining what you tried.
• Never ask a user for their password or verification codes.

7. Communication and representing Voznest

• Don't speak publicly on behalf of Voznest unless that's your role. Announcements go through Community and Marketing.
• Don't share unreleased features, internal decisions or cases on social media or in other communities.
• Don't accept gifts, money or favours in exchange for decisions or access.

8. Consequences

Breaking these rules is handled from your record, in proportion to how serious it is and whether it happened before:

• Verbal warning.
• Written warning.
• Final warning.
• Suspension from the team.
• End of the collaboration (dismissal), with all access removed.

Serious breaches — abusing permissions, leaking data, fake attendance or proof, harassment — can lead straight to dismissal. Every warning and decision is written down, you receive it by email, and you can always talk to People & Recruiting.

9. Leaving the team

• You can resign from My record; a notice of 7 days is recommended.
• When you leave, all your access is removed and you receive a service certificate with your dates and hours.
• Confidentiality continues after you leave.

10. Raising concerns

If you see something wrong — a teammate abusing permissions, unfair treatment, a security problem — tell your manager, People & Recruiting or Security. Reporting in good faith never counts against you.