Whether you're starting up a Studio Project for the first or hundredth time, there are some set-up steps you need to take. If you don't already have an account on a Studio Server (either one your organization is running or Bluebeam's free server), you will need to establish one first (if you've ever signed into a Studio Project or Session before, you already have one of these). See Create a Bluebeam Studio Server Account to set one up on Bluebeam's open Studio server or Create and Manage Studio Accounts for more information about configuring Revu to use your own Studio server. Then it's simply a matter of creating the Project and uploading the initial document set you want to share, configuring its settings and permissions, and finally inviting guests to the Project.
While access to Studio Project PDFs is supported on Bluebeam Revu, Vu, and Revu for iPad, new Studio Projects can only be started in Revu for Windows. You will need a validated Studio account to create a Studio Project. If you have not established one yet, do that first.
During the creation process, you will be given an opportunity to upload Project files. If you're not quite ready for that yet, or if you need to upload additional documents later, you can do so quite easily.
To start a new Studio Project:
Enter a name for the Project and click OK. The Studio tab changes to show the empty Project.
To add initial Project files, select from the following options:
Additional files and folders can be added to the Project later as well.
By default, no other users are granted access to a new Project and permissions for any who are invited are very limited. You can change these conditions by configuring the Project Settings.
Adding a user to a Project lets you to allow them access (for Projects that are set to restrict attendee access) or deny them access (for Projects that are not set to restrict attendee access). Restricted attendee access is discussed in more detail below.
Click the User Access tab. Previously added users will appear in the list.
Permissions define what actions users can take in the Project. Permissions can be defined for groups as well as individual users.
Click the Permissions tab.
The default group, Everyone, will be shown, as well as any other Groups that have been previously added to this
Select the desired user or group and click OK. By default, when users and Groups are added they inherit the permissions of the Everyone group.
Note: Individual users will not appear in the list until after they have accessed the
If you would like to create a new Group or change the membership of an existing one, click
Note: When creating Groups, keep in mind that Revu will allow somebody to be in multiple Groups within the same Session
Administrators can manage Permissions for other
There are some limits on what administrators can do, however:
When setting permissions, there are two sets of hierarchies to keep in mind: Permission Sets and Permission States.
Permission States work within Permission Sets and generally come into play only to resolve conflicts that arise when a user is a member of two or more Groups that have conflicting permissions (see examples 4 and 5 below for further illustration). It is generally recommended that people not be added to multiple Groups, but in the event that it is necessary, Hosts and administrators should coordinate to ensure that the proper permissions are granted.
The hierarchies are:
- Individual permissions (that is, those set up for a specific user) have primary importance.
- Group permissions (that is, those set up for a Group you have created) have secondary importance.
- General permissions (that is, those set up for the default
Everyonegroup) have the least importance.
- Explicit Deny (that is, a permission that is specifically set to Deny) has primary importance.
- Explicit Allow (that is, a permission that is specifically set to Allow) has secondary importance.
- Inherited State (that is, any permission—whether it is Deny or Allow—that is inherited from the default
Everyonegroup) has the least importance.
With these hierarchies in mind, here are a couple examples that should help illustrate how a user's actual permissions are determined:
You can create new folders in the Project, select individual files to upload, or upload an entire folder and its contents if you have the appropriate permissions.
To add files to a Project:
When in the Project, right-click the Project name or a folder within the Project and select the desired option:
Inviting somebody to a Project automatically adds them as an Allowed User in the Project Settings (see "Setting User Access in the Studio Project" above for more information about User Access). In addition, the invitee is also sent an email containing information about the Project as well as a link allowing them to automatically connect to the Project.
To invite a user to the Project:
When in the Project, click Invite on the Studio tab. The Project Invitation dialog box appears.
To add invitees from the address book of your default email program, click Address Book.
Note: The email program must be MAPI compliant for Revu to access its address book. The address books from web-based email like Gmail, Hotmail or Yahoo cannot be accessed.