Skip to main content
Organization membership and project membership are separate. An organization Owner can access its projects, while other organization roles do not automatically grant access to projects the person has not joined. See Organizations and projects. You need permission to manage members in the relevant scope. The project member controls are available to project Owners and administrators. Role options and management controls can depend on the organization’s configuration. The member and role tabs are part of the people and permissions settings. Depending on the settings view, the section may be titled People & Permissions; in Project settings, use the Members and Roles tabs directly.

​
Invite someone to an organization

  1. Select the organization and open its Organization settings, then Members.
  2. Choose Invite, enter the person’s Email address, and select a Role. The invitation form offers Member and, when permitted, Owner.
  3. Choose Invite. Check the member list for the person and their role.
An invitation manages ThinkPlatform membership. It is separate from Microsoft Entra sign-in and does not automatically add a Member to every project.

​
Add a project member

  1. Select the organization and project, and open Project settings and Members.
  2. Choose Add member, select an existing organization member, and choose Owner or Member.
  3. Submit the dialog and check the project member list and role displayed for that person.
If the person is missing from the selection, first check their organization membership. If the control is unavailable, check your own project role and selected project.

​
Change roles or remove a member

In the appropriate organization or project Members list, use Roles beside the member to review or edit their roles. Use the member’s actions menu to remove them when access is no longer needed. Confirm the change in the list and ask the person to verify the intended access. The interface prevents editing or removing your own membership through these controls. Changes can be rejected to preserve required ownership or enforce authorization; review the message and involve another authorized owner when needed. The Roles settings can include Owner, Member, Reader, and custom permission bundles where configured. Review a role’s permissions and scope before assigning it. Preset roles are immutable; custom roles allow a more specific set of permissions. An effective permission can also depend on resource-specific access settings.