Skip to content
Select language: English

Sharing and teams

Copy for AI
Use AI with help

Sharing settings decide whose records a person can reach when their role gives them Own records only. Use them to keep records private, open them to a team, or share them with the whole company. See Roles and sharing for the ideas behind them.

You need System View to see these settings and System Edit to change them. They affect only people whose role is at Own records only for the action: All records already reaches everything, and No access reaches nothing.

Who sees a record: the role’s level for the action decides first. No access shows no records, All records shows every record in your company, and Own records only shows the records you own plus those the sharing settings add through Default access, Sharing rules, Teams and Reports to.Your role’s levelfor the action, in thatmoduleNo accessno recordsAll recordsevery record in yourcompanyOwn records onlyrecords you own, plusshared onesSharing settingsDefault access,Sharing rules, Teams,Reports toadds
  1. Open System settings and select Sharing & teams in the Users & security group.
  2. On Reports to, choose who each user reports to.
  3. On Teams, select New team, enter a Name and, if it sits under another team, a Parent Team. Select Manage members, add people with Add member, and mark any Team Leader.
  4. On Default access, choose the Default access for each record type, switch Grant Access Using Hierarchies on or off, then select Save at the foot of the page and confirm Save default access?.
  5. On Sharing rules, select New sharing rule. Choose the Object, the team whose records are shared under Records owned by, the team under Shared with, and the Access: Read Only or Read/Write. Select Save.

A change on Reports to is saved as soon as you make it. Changes on Default access are saved when you select Save and confirm, because they decide which records colleagues can open; teams and rules are saved when you select Save in their dialogs. People see the new reach the next time they open a list or record. A reporting line that loops back on itself is refused.

  • Private: only the owner and the people above them. Private + Alert is the same, but someone creating or searching for a record that already exists sees its name and owner, without opening it.
  • Team: everyone on the same team as the owner can see and edit the record. Team leaders also reach the teams below theirs.
  • Public Read Only: everyone can see; only the owner and those above them can edit. Public Read/Write: everyone can see and edit; a red warning under the choice says so.
  • Controlled by Parent (contacts only): whoever can see the account can see its contacts. Not set (current behaviour) keeps the contact list following the account’s owner.
  • The Result column beside each record type says in one sentence what its current setting does.
  • Grant Access Using Hierarchies is on until you turn it off: people above the owner in Reports to get the same access as the owner.
  • A Team Leader reaches the records of everyone in the teams they lead and in the teams below.
  • A sharing rule opens one team’s records to another team. A rule from a team to itself is refused: a team already sees its own records.
  • Sharing never exceeds the role: seeing a record needs View, and changing it needs Edit.
  • A team or rule switched Off stops sharing; neither is deleted.

Customers belong to the person who looks after them. Starting from the owner keeps each salesperson’s contacts, prices and pipeline with them, which protects your customers’ details and avoids two people chasing the same lead. You then open access on purpose, never by accident.

Managers see through the reporting line, not through a bigger role. With Reports to and hierarchies on, a manager reaches their team’s records while staying at Own records only. They can coach and cover for their team without also seeing every other team in the company.

Rules work team to team. People join and leave; teams last longer. A rule written for a team keeps working when a new designer joins it, with no rule to rewrite.

A change to default access asks first. It changes what everyone at Own records only can open at once, so easySales asks you to confirm before it saves.

  • Set the reporting line once. Choose each user’s manager on Reports to; with hierarchies on, managers need no wider role. See Ownership and visibility.
  • Read the Result column before you save. It says in plain words what each setting will do, so you can check the effect without testing it on a colleague’s account.
  • Use Private + Alert to stop duplicates. Staff who search for a customer that exists under a colleague see its name and owner, so they ask instead of creating it again. See Duplicate alerts.
  • Make the team leader the manager. A Team Leader reaches every member’s records and the teams below, with no extra rule.
  • Switch a rule off instead of deleting it. Off keeps the rule ready for the next project that needs the same opening.

Lim & Co’s designers are on a role at Own records only. Mei Tan sets Account to Private and records that Ahmad and Priya report to her. Ahmad sees only his own accounts; Mei sees hers, Ahmad’s and Priya’s.

To let the “Studio B” team read the quotations of the “Studio A” team, she adds a sharing rule on Quotation from “Studio A” to “Studio B” with Read Only.

How many accounts a manager sees. Mei owns 20 accounts, Ahmad 12 and Priya 9. With Grant Access Using Hierarchies on, Mei’s list shows 20 + 12 + 9 = 41 accounts. Ahmad’s shows his 12, and Priya’s her 9. If Mei turns hierarchies off for Account, her list drops back to her own 20.

A customer that already exists. Account is set to Private + Alert. Ahmad starts to create Harbour Café, which Mei already owns. easySales shows him the name and that Mei owns it, but he cannot open it, so he asks Mei to add him to the Account Team instead of creating a duplicate. See Duplicate alerts.

  • How do I let a whole team see each other’s customers? Set Account to Team on Default access, and put the people in the same team on Teams. Everyone on the team can then see and edit the team’s accounts.
  • What does Private + Alert mean? Records stay private to the owner and those above them, but someone creating or searching for an existing record sees its name and owner. They cannot open it.
  • Does a sharing rule let people delete records? Only if their role allows it. Sharing never goes beyond the role: Read/Write lets people edit only if their role has Edit, and delete only if it has Delete. Read Only never lets them change or delete anything.
  • Why did a sharing change make no difference for some users? Their role is at All records, which already reaches every record, or at No access, which reaches none. Sharing affects only Own records only.
  • Can I share records with one person only? Rules work between teams. Make a team for that person, or add them to an account team on the customers they need.
  • What happens when I switch a team off? It stops sharing, and its members lose the access it gave. The team is kept, so you can switch it on again.