Skip to content
All guides

Business tools

Seasonal Staff: Bought Yandex Accounts or Yandex 360 Mailboxes?

Yandex 360 for Business has two kinds of employee account. Domain mailboxes stay with the shop; invited personal accounts stay outside it. Who must keep the season's mail decides which one each helper gets.

Contents

The question to answer before the season starts

A small shop that already runs Yandex 360 for Business takes on three helpers for the busy months. Each needs a Yandex login to reach the shop's shared tools. The real question is not how to create those logins but who must keep what they write: will the shop need the helpers' mail and files after the season, or only during it?

Yandex 360 offers two kinds of employee account, and they answer that question differently. A bought personal Yandex account fits one of them. The other is a mailbox on the shop's own domain, which no listing can replace.

Domain accounts and invited accounts compared

Yandex 360 admin help describes domain accounts as accounts created on the company's connected domain. Administrators can edit their data apart from the username, set passwords, block and unblock them, manage aliases and delete them. Deleting one is final: the employee loses all data on Yandex Disk and in Yandex Mail, and it cannot be restored. Blocking keeps the information and can be undone.

Invited accounts are personal Yandex accounts that join through an invitation link, with no domain needed. Administrators cannot edit or block them; they can only remove them, after which the person loses access to company services and is removed from its departments and groups. The account itself, with its own mail, carries on outside the organization.

What Yandex's 360 terms add

The General Terms of Use for Yandex 360 say employee accounts belong to the corporate client and may be modified or deleted by it. Personal accounts created independently in Yandex ID and then invited are an exception to that ownership rule, but the terms add that the inviting organization, through its administrators, may access their data, manage them, configure access and impose restrictions; the terms state that the owners of such accounts are hereby notified of this.

So an invited personal account is not invisible to the shop while it is inside the organization. It simply does not become the shop's property, and it leaves with its holder.

Three seasonal helpers, worked through

Hypothetical: a garden shop hires three helpers for spring. One answers customer orders by email; the shop must keep that correspondence for later questions about deliveries. The other two pack orders and only need the shared calendar and a Disk folder of packing lists.

The order-desk helper gets a domain mailbox. At the end of the season the shop blocks it rather than deleting it, so the correspondence stays available. The two packers neither need nor want a domain address. One already has a personal Yandex ID; the other does not want to use his private account for work, so the shop buys him a separate Yandex account that he takes over himself, replacing the phone and recovery details with his own. Both are invited and removed when the season ends.

How to decide for each helper

Give a domain mailbox to anyone whose work mail or files the shop must keep, or whose messages customers should see coming from the shop's domain. Remember that deleting that account destroys its mail and Disk data, so block it at the end of the season unless you are sure nothing in it is needed.

An invited personal account fits a helper who only needs access to shared tools and whose mail need not stay with the shop. A bought account is the answer when that helper has no Yandex ID or prefers not to use a private one. Each person uses their own login, held in their own name; the shop does not keep a pool of logins for helpers to pass around.

Put the end of the season into the plan from the start. Note for each helper which kind of account they have and what happens on their last day: block the domain mailbox and keep it, or remove the invited account from the organization. Tell helpers with invited accounts before they join, so nobody is surprised by what the shop can and cannot do with their login.

Choosing the listing for a helper's account

Because the helper will hold the account personally, the listing must let control pass cleanly. Prefer one that says the account is clean, states whether a phone is linked and whether it can be replaced, and includes the backup email and security question. Age is irrelevant to this job.

Leave enough time before the season. Yandex ID Help says the secure number can only be replaced, and without access to the old number the change takes effect after 14 days. The helper should finish the takeover before accepting the shop's invitation.

Terms, independence and ordering

Yandex's user agreement asks for valid registration details, makes the holder responsible for actions under the account and does not allow reselling access to Yandex services without Yandex's authorization; the 360 terms also bar transferring rights under them to third parties unless the agreement allows it. A listing does not give Yandex's permission, so follow Yandex's terms and make sure the helper's details are the ones on the account.

rStock is an independent marketplace and has no affiliation with Yandex. The order is paid from your rStock balance, and the delivery appears as a record on the order page with the window for opening a dispute. Check the account within that window, then compare the Yandex accounts in the category for the helpers who need one.

Frequently asked questions: Seasonal Staff: Bought Yandex Accounts or Yandex 360 Mailboxes?

Keep reading