课程章节
培训 · 课程 5. 团队和管理 · 第 5.1 章,共 6 章
5.1 组织和成员 2:45
创建组织、添加成员,并将项目纳入其中。
演示 Holarch 2.20。
您将学到
- 创建组织并成为其第一位组织管理员
- 将某人以成员或组织管理员身份添加到组织
- 从项目的“共享”对话框将项目关联到组织
- 说明为什么组织成员身份不提供对项目的访问权限
- 在账户设置中查看您方案的项目限制
在 Holarch 中建立团队:为 Plant Inspection Drone 团队创建组织,查看组织管理员控制的设置,添加成员,使项目归属于组织,以及方案限制和班级状态的作用。
练习
在 Holarch 中基于 CubeSat EO-1 演示项目亲自完成此操作。
- 打开 账户设置,找到 组织,输入
EO-1 Practice Team,然后单击 创建组织。 - 打开 组织设置,单击该组织所在行,在 成员 下通过 添加成员 将第二个电子邮件地址(同事的地址或您自己的另一个地址)添加为 成员。
- 打开您的 EO-1 演示项目(如果没有,请创建:管理项目 → 项目文件 ▾ → 新建演示项目 → CubeSat(引导式系统工程))。单击 共享,在 组织 下选择
EO-1 Practice Team,然后单击 完成。 - 在 管理项目 中选择该组织的文件夹树,单击 新建文件夹,将其命名为
Spacecraft,然后将 EO-1 项目拖到其中。 - 打开 账户设置 → 方案(或 方案与账单),记下您的项目可以容纳多少编辑者和条目。
当 EO-1 位于组织树的 Spacecraft 文件夹中,且第二个地址列为成员或待处理的邀请时,即完成练习。
自测
- 您将一位同事添加到了组织中。对方现在能打开 EO-1 项目吗?
- 谁可以使项目成为组织的一部分?
- 为什么要保留第二位组织管理员?
- 组织管理员能看到组织项目的哪些内容?
显示答案
您将一位同事添加到了组织中。对方现在能打开 EO-1 项目吗?
不能。组织成员身份不提供对其项目的访问权限。项目所有者需要在“共享”对话框中与其共享项目并为其分配角色。
谁可以使项目成为组织的一部分?
只有项目的所有者之一,在 共享 → 组织 下进行。组织管理员不能关联项目;他们管理成员和组织的设置。
为什么要保留第二位组织管理员?
组织始终至少需要一位组织管理员,因此无法移除或降级最后一位。第二位组织管理员可以在第一位不在时管理成员和设置。
组织管理员能看到组织项目的哪些内容?
名称、成员和设置,但看不到项目内容。要打开项目,必须由所有者与其共享。
延伸阅读
文字稿
显示文字稿 (旁白和屏幕内容)
Introduction
Welcome to Teams and Administration. This track is for the person who sets Holarch up for a team: who belongs, who may do what, how people sign in, and how AI and other tools reach your projects.
The examples use the Plant Inspection Drone project from the migration track.
Create an organization
An organization groups the people and projects of one team or company. Open the account menu at the top right, and choose Account Settings.
On screen: Account menu → Account Settings.
Under Organizations, type the team's name, and click Create Organization. Whoever creates it becomes its first org admin.
On screen: Organizations → name → Create Organization.
Organization settings
Org admins manage the organization from the account menu, under Organization Settings. Click the organization to open its settings.
On screen: Account menu → Organization Settings → the organization.
Its settings come in groups that apply to every project of the organization: the members, the plan, what AI may do, API access and two-step sign-in, and whether it is a class.
On screen: AI, API access, Sign-in, Class.
Members
Members come first. Add a colleague by email address, as a member. People without an account get an invitation, and join when they accept it.
On screen: Members → email → Member → Add Member.
Add a second person as an org admin. Org admins manage the members and these settings; they have no access to other organizations.
On screen: [email protected] as Org admin → Add Member.
Projects
Members do not see each other's projects automatically. A project belongs to the organization when its owner chooses it under Share. Open the drone project, click Share, and choose the organization.
On screen: Manage Projects → Plant Inspection Drone → Share → Organization.
From now on, the organization's switches apply to this project. Sharing still decides who may open it, and with which role, as the next chapter shows. Click Done.
On screen: Done.
Plans and classes
Each project follows its owner's plan: how many items it holds, how many people may edit it, and how long its versions are kept. Account Settings shows your plan and its limits. Reviewers and viewers never count.
On screen: Account Settings → Plan.
Teaching a course? An org admin can ask for class status in Organization Settings. A class organization lets student groups of up to six work in one project, and instructors' projects hold fifty.
On screen: Organization Settings → Class.
Recap
Let's recap. You created an organization, saw the four switches an org admin controls, added a member and an org admin, brought a project into the organization, and found your plan's limits and class status.
Next, you decide what each person may do in a project, and how requirements get approved.