Screens: Projects

Sharing and members

In the Project Share Settings window you invite team members to an account project, and change or remove their roles. What each role can do is set in the Project settingsRole Permissions tab of the project settings. Why roles and permissions are split this way, and what you see together with your team, are explained in Collaboration and permissions.

Where you can use itWebDesktopWithout signing inSigned inLocal projectsAccount projects

What's on the screen

Click the Collaborate button in the header to open the Project Share Settings window. When the project has two or more members, the button shows their overlapping avatars instead, and clicking it opens the same window.

No.NameDescription
1Invite Team Members fieldSearch for a user by nickname or type an email address. You can add several people at once. Visible only to the owner and to members whose own role has Share Permission or All Permissions.
2Team MembersTeam members and their roles. Your own row has the You label. Members suspended after a plan downgrade have the Disabled label.
3Member menuThe ⋮ button at the right of a member's row. For the owner it has role items, Transfer Ownership and Remove Member. For a Manager it appears only on the rows of DBA and Member members and has only Remove Member (see 'Changing roles and removing members' below).
4Pending InvitationsInvitations not yet accepted. Visible only to the owner; the ✕ button on the right cancels an invitation.
5Invite buttonInvites with the Member role. Click the arrow on its right to invite with another role.

Members other than the owner see a Leave Project button at the bottom of the window.

Roles

RoleCan invite asMember management
OwnerManager, DBA, MemberChanges the role of and removes any member, and transfers ownership. There is one per project.
ManagerWith the Share Permission item on, DBA, MemberRemoves DBA and Member members. Cannot change roles.
DBA, MemberWith the Share Permission item on, MemberNone.

Roles other than the owner can invite only when their own role has the Share Permission or All Permissions permission (the Share Permission item in the table above). In a new project only the Manager role has Share Permission on. Older projects whose owner has never saved the role permissions follow the same defaults. If there is no role you can invite as, the Invite Team Members field and the invite button do not appear.

Inviting team members

  1. Open the account project and click the Collaborate button in the header.
  2. In the Invite Team Members field (1), type a nickname and pick the user, or type an email address and press Enter. Existing members, people already invited and yourself cannot be added; a message appears under the field.
  3. Click the invite button (5). To invite with another role, click the arrow on the right of the button and pick the role.
  4. The invitation appears in the Pending Invitations list (4). The recipient gets an invitation email, and a user who already has an account also gets the invitation in NeoSQL notifications.
  • An invitation can be accepted for 7 days after it is sent. Inviting the same email again resets the role and the deadline.
  • The recipient accepts by clicking the link in the invitation email and accepting on the website, or by selecting the invitation in the app's notifications and clicking the Accept button. They must be signed in with an account whose email matches the invited email.
  • The number of members is set by the project's plan. If you invite more people than there are seats left, nothing is sent and you are told. Someone who accepts after the seats are full joins in the Disabled state. Seats are explained in Plans and features.

Changing roles and removing members

  1. Click the ⋮ button at the right of the member's row.
  2. Pick a role item (1) to change the member to that role. Only the owner can change roles, so other people's menus have no role items.
  3. To remove the member, pick Remove Member (3) and confirm.
  • Members whose role changed or who were removed get a notification. A member who has the project open is asked to reopen it when their role changes, and is taken out of the project when removed.
  • The owner removes any member other than the owner; a Manager removes only DBA and Member members. A Manager's menu has only the Remove Member item.
  • The owner cannot be removed. Any member other than the owner can leave on their own with the Leave Project button at the bottom of the window.

Transferring ownership

The owner transfers ownership with the Transfer Ownership item (2) in a member's menu. The previous owner becomes a Manager.

ProjectCan be transferred toPlan
A project created with your own planAny member. It is refused if the recipient's plan is lower than yours.It follows the recipient's plan.
A project in a workspaceThe workspace owner or an active member of that workspaceIt keeps following the workspace owner's plan.

The workspace owner takes back ownership of a project owned by a member with the Reclaim Ownership item in the ⋮ menu of the owner's row in the Project Share Settings window. The previous owner becomes a Manager. Workspaces are explained in Workspaces.

Setting role permissions

  1. With the owner's account, click the Project Settings button in the header and open theProject settingsRole Permissions tab. This tab is visible only to the owner of an account project and to roles with All Permissions, and only the owner changes it.
  2. Open one of Manager, DBA and Member in the role tabs (1). The owner always has every permission and is not in the list.
  3. Check or uncheck items and save the project settings window.
No.ItemWhen checked
2All PermissionsTurns on all the allowing items below, including project settings, and turns off all the restricting items. The items below can no longer be changed.
3Share PermissionThe Invite Team Members field appears in the Project Share Settings window and the member can invite. A Manager invites as DBA or Member, other roles only as Member.
4Connection PermissionViews, adds, edits and deletes connections.
5ERD Delete PermissionDeletes team ERDs. Without it, even the creator of a team ERD cannot delete it.
6Sensitive Data Masking(Restriction) Sensitive columns and pattern matches are shown masked. Explained in Column masking.
7Watermark Enforce(Restriction) Printing an ERD always adds the project's watermark. It can be changed only on plans that let you set the watermark text.
8DDL Restriction(Restriction) DDL cannot be run directly and is requested for approval instead. Checking it turns off Connection Permission. Explained in DDL approval.
9Domain restriction(Restriction) Domains can only be used; pinning domain packs to connections and managing domains are not available.

The items that are on in a new project are listed in the role table of Collaboration and permissions.

Things to keep in mind

  • If the project's plan allows only one member, the Collaborate button does not appear even in an account project.
  • The Project settingsRole Permissions tab is also visible to roles with All Permissions, but read-only. The Only the project owner can change role permissions and the watermark. You can view the current values. notice appears above it and the items cannot be changed. Change role permissions with the owner's account.
  • When a plan downgrade leaves more members than seats, the extra members become Disabled and cannot enter the project. When a seat frees up, the owner lets them back in with the Enable button on their row. The cleanup is explained in Manage Subscription.
  • Inviting someone to a workspace does not share any project. The difference between the two invitations is explained in Collaboration and permissions.