访问控制

Supabase 提供了详细的访问控制，可以管理你在组织和项目中的权限。

🌐 Supabase provides granular access controls to manage permissions across your organizations and projects.

对于每个组织和项目，成员可以拥有以下角色之一：

🌐 For each organization and project, a member can have one of the following roles:

• 所有者：对组织和项目资源中的所有内容拥有完全访问权限。
• 管理员：拥有对组织和项目资源的全部访问权限，但不包括更新组织设置、将项目转移到组织外，以及添加新所有者。
• 开发者：只能读取组织资源，对项目资源有内容访问权限，但不能更改任何项目设置。
• 只读：只能读取组织和项目资源。

当你第一次创建账户时，会为你创建一个默认组织，并将你设置为所有者。你创建的任何组织也都会把你设置为所有者。

🌐 When you first create an account, a default organization is created for you and you'll be assigned as the Owner. Any organizations you create will assign you as Owner as well.

管理组织成员 #

🌐 Manage organization members

要邀请他人协作，请访问你组织的团队设置以发送邀请链接到其他用户的邮箱。邀请有效期为24小时。对于项目范围的角色，发送邀请时你只能为用户分配单个项目的角色。用户接受邀请后，你可以为多个项目分配角色。

🌐 To invite others to collaborate, visit your organization's team settings to send an invite link to another user's email. The invite is valid for 24 hours. For project scoped roles, you may only assign a role to a single project for the user when sending the invite. You can assign roles to multiple projects after the user accepts the invite.

使用管理 API 查看组织成员 #

🌐 Viewing organization members using the Management API

你也可以用管理 API 查看组织成员：

🌐 You can also view organization members using the Management API:

1
# Get your access token from https://supabase.com/dashboard/account/tokens
2
export SUPABASE_ACCESS_TOKEN="your-access-token"
3
export ORG_ID="your-organization-id"
4
5
# List organization members
6
curl "https://api.supabase.com/v1/organizations/$ORG_ID/members" \
7
  -H "Authorization: Bearer $SUPABASE_ACCESS_TOKEN"

转让组织所有权 #

🌐 Transferring ownership of an organization

每个 Supabase 组织必须至少有一个所有者。如果你的组织里有其他所有者，你可以通过点击组织团队的离开团队在设置中放弃所有权并离开组织。

🌐 Each Supabase organization must have at least one owner. If your organization has other owners then you can relinquish ownership and leave the organization by clicking Leave team in your organization's team settings.

否则，你需要邀请某个用户作为所有者，并且他们需要接受邀请，或者在你离开组织之前，将现有的组织成员提升为所有者。

🌐 Otherwise, you'll need to invite a user as Owner, and they need to accept the invitation, or promote an existing organization member to Owner before you can leave the organization.

组织范围角色 vs 项目范围角色 #

🌐 Organization scoped roles vs project scoped roles

组织中的每个成员都可以被分配一个角色，这个角色可以针对整个组织，也可以针对特定项目。

🌐 Each member in the organization can be assigned a role that is scoped either to the entire organization or to specific projects.

• 如果某个成员拥有组织层级的角色，他们将在该组织内所有当前和未来的项目中拥有相应的权限。
• 如果某个成员被分配了项目范围的角色，他们只会有权限访问分配给他们的特定项目。他们无法查看、访问，甚至在 Supabase 仪表板上看到组织内的其他项目。

这样可以实现更细致的控制，确保用户只看到并访问与自己角色相关的项目。

🌐 This allows for more granular control, ensuring that users only have visibility and access to the projects relevant to their role.

不同角色的组织权限 #

🌐 Organization permissions across roles

下表显示了每个角色可以对组织的资源采取的操作。

🌐 The table below shows the actions each role can take on the resources belonging to the organization.

不同角色的项目权限 #

🌐 Project permissions across roles

下表显示了每个角色可以对项目资源执行的操作。

🌐 The table below shows the actions each role can take on the resources belonging to the project.