Teams & shared groups
3:05 MINTour team membership and group-sharing controls in AiCopal. Learn permission levels through an anonymized example without inviting or adding members.
Try it as you go.
Watch a step. Pause. Make it yours.
- Inspect the team, member roles and invitation controls.
- Open Share for a project and review what teammates could see.
- Compare access levels. This example stays Not shared; no invitation or second-member workflow is demonstrated.
Read the transcript
A project has people, and it has conversations. Teams organize the people. Groups organize the sessions you want to work with. In this chapter, we will inspect team management and the sharing controls for our fictional Willow Cafe project. Names and meeting details are changed for this demonstration. The controls and access state are real.
In Settings, open Teams when it is available for your account. New team name and Create team are the starting controls for a new team. This account already has a team, so we open that existing entry. The list shows one member. Opening a team is not the same as sharing a project with it.
The detail panel shows the team name and its members. Our anonymized example shows Maya as Owner. Save belongs to the team name field. Check your own role before expecting to manage other people; the controls available to you depend on your access.
Invite someone has an email field, a role selector, and Send invite. Review the recipient and intended role carefully before sending a real invitation. This tour does not send one or add another member. Membership and sharing are separate: inviting a person to a team does not automatically share every private conversation.
Now choose the project group you intend to share. In Groups, expand the Willow Cafe project and choose Share. The dialog identifies the group and lists the teams you can choose. Check that name before changing any access.
Read the notice at the top. People on teams you choose can read the summary and transcript of every session in this group. Your own chat with the assistant is not included in that shared view. Review the group's sessions before sharing; a familiar team name is not a reason to skip that check.
The permission menu is set to Not shared in this example, and the message confirms that this team cannot see the group. Opening the dialog has not granted access. When you intend to share, choose the level that fits the work, and verify the resulting state.
Can view allows reading the sessions and conversation. Can add sessions also allows people to contribute their own sessions, write in the conversation, and edit its name and description. Can manage adds the ability to remove sessions from the shared group. These group permissions are separate from the team roles we saw in Settings.
Sharing needs a connection. The app does not save this shared view for offline use. Do not assume a teammate's shared material is available offline, or that personal search automatically covers it.
Start with the right people. Choose the right group. Give only the access needed, then check the result. This tour leaves the example not shared and does not demonstrate another member's view. Use your own authorized team workflow to verify what a teammate can see before relying on it. Keep private grouping and shared collaboration distinct.
Download transcript · Download captionsPublished by AiCopal Studio | Guide text reviewed . Video recording dates vary.
Preview lessons · Recorded with a fictional Willow Cafe project. Some generation waits are shortened. Controls may vary by version.