Let's revisit the organization setup page. Remember, the Admin enters the organization setup by clicking the gear icon under her organization's name. We're going to focus on the Teams section right now. The other sections aren't helpful without proper team setup.

By default, ASW creates five teams for you. You can modify them, delete them, or create teams of your own. Let's look closer.

1. The initials, name, and color of the team.

2. Clicking the triple-dots presents the choices "Details" and "Remove".

 - Remove will delete the team. If you remove a team, it is gone for good. So be sure before you commit to this. ASW will warn you before allowing you to fully remove the team.

 - Details is where you can make changes to the team. We'll see what that looks like in a moment.

3. The [+] button is used to add a team. When you click this button you'll be prompted to enter a Team Name and a Team ID.

NOTE - if the Team ID has been used in the system before you will be warned of that fact. Just add digits or some other signifier until you have a unique ID.

Before you add a team, let's see what happens with that information

Whether you add a team, or just click Details on an existing team, this is the view you'll see.

1. Click here to change the color assigned to the team. Multiple teams could have the same color, but it may be more helpful to assign a different color to each team.

2. The team name. This can be changed here.

3. The team URL which will display at times in the browser address bar. (If you recall what happens when you add a team, this is what was referred to at that time as the "Team ID".)

4. The job view selector. We'll cover this in more detail soon.

5. The permissions of the team. We'll cover these in more detail soon as well.

6. Don't forget to click [Save] after you've made any changes.

7. The list of members currently assigned to the team. You can click the trash icon to remove a member. This does not delete the user's account. Likewise, it does not remove a member from the organization, it just removes the member from the team.

8. You can use this button to add a member of your organization to the team. But since the Admin hasn't added any members to the organization yet, we'll ignore this for now.

Let's take a look at the different job view options available. If you click the arrow in area 4, you'll see the following choices:

Assigned - team members can only see jobs assigned to them.

Assigned & Unassigned - team members can see jobs assigned to them, as well as jobs available for assignment.

All - team members can see all jobs, including drafts and completed jobs.

None - team members can't see any jobs at all.

Edit Jobs - team members will be allowed to edit job details. A team member with this permission can draft a job in ASW and can change the name of a job in ASW.

Reassign Jobs - team members are allowed to change the assignment of a job.

Submit Jobs - team members are allowed to submit audio files for ASR processing, which is how jobs are created to begin with.

View Job Cost - team members can see the cost associated with a job.

View Cases- team members can view case contents.

Edit Cases- team members can edit the details of cases.

Edit Job Transcript - team members can edit the transcript of a job in AutoScript Desktop (ASD). Used in combination with the "Assigned" job view, the team member can only edit jobs assigned to them.

Proofread Job Transcript - team members can proofread the transcript in ASD. Job view settings are a powerful combination here as well.

Finalize Job Transcript - team members can proofread and finalize the transcript in ASD.

Mark Job Complete - team members can mark the status of a job in ASW as complete.

View Billing - team members can see the details of the billing account(s).

Manage Billing - team members can edit the details of the billing account(s).

Manage Packages - team members can change the plan tier (formerly known as packages).

View Licenses - team members can see the details of the organization's AutoScriptOne subcriptions. Only applies to Beta testers at this time.

Manage Licenses - team members can edit the details of the organization's AutoScriptOne subcriptions. Only applies to Beta testers at this time.

View Reports - team members can view reports. See NOTE below.

Manage Members - team members can manage other members (just like our Admin is about to do very soon).

Manage Permissions - team members can manage team permissions, just like we're doing now.

Manage Workspaces - team members can change the details of workspaces (we'll look at those after the teams are ready).

Manage Organization - team members can change the details of the organization, the first steps our friend the Admin took when she logged in under the organizational account.

NOTE - The Manage Organization permission changes the widgets displayed on the Dashboard. Members of teams with this permission will see: Organization Members, Workspaces Activity, Performance Review, and Daily Active Members. Members of teams without this permission will see: My Efficiency, Number of Jobs to Claim, My Jobs List, and Jobs Available to Claim. All teams will see the Deadline Calendar.

BIG NOTE - Before we close the Owner team, we need to talk about it real quick. Although there is nothing to stop you from adding members to the default Owner team, it was intended for use only by the account that created and therefore "owns" the organization. If you used an organization email to create the account, it would also make sense to add the company owner's account to this team. Outside of those people, if you need a team with the same level of permissions, it is highly recommended that you make another team and give that team the same permissions. Our fictional Admin will do that in a few moments.

We've seen what the default Owner team looks like. Now let's look at the permissions of the other default teams.

Operations -- View jobs: All -- Permissions: Edit Jobs, Reassign Jobs, Submit Jobs, View Job Cost, View Cases, Edit Cases, Edit Job Transcript, Proofread Job Transcript, Finalize Job Transcript, Mark Job Complete, View Reports, Manage Members, Manage Permissions, and Manage Workspaces

Editor -- View jobs: Assigned & Unassigned -- Permissions: Edit Job Transcript

Proofer -- View jobs: Assigned & Unassigned -- Permissions: Proofread Job Transcript

Billing -- View jobs: None -- Permissions: View Billing, Manage Billing, Manage Packages, View Licenses, Manage Licenses, and View Reports

These default teams almost meet the needs of RemoteProofs, but not quite. Our Admin will:

- Add a team called "RP Admins"; this team will have the same permissions as the default Owner team.

- Modify the Operations team name to "RP Ops".

- Finally, she will change the team colors to reflect the company colors.

Here's how things look for our plucky Admin now.

Now the Admin just needs to set up workspaces so the teams have a space to, well, work.