Control at Your Hands

Permissions are what makes Project Butterfly’s collaboration flexible and fit for any task. There are two kinds of permissions in Butterfly:

  • Edit – Your collaborator can edit the drawing, draw new objects, and edit annotations.
  • Download – Your collaborator can save the DWG file to his computer, and save a copy of the drawing to his own Butterfly account.

You can set permissions to shares, co-edit sessions and reviews. Permissions are set per recipient, and you can change them at any time.

When to use permissions?

If you’re collaborating with a person you totally trust, there’s no problem leaving the default permissions – allow edit and allow download. However, if you’re collaborating with a colleague or someone less experienced, consider setting permissions.

Let’s say you want to show your client some progress on a particular design. The best choice is to start a co-edit session with your client. Seeing as the client does not have previous CAD experience, you might want to restrict him from editing the drawing. This way the co-edit session goes on smoothly and with no damage to the drawing.

Another common scenario is when professionals from different firms and fields collaborate. Let’s say you’re sharing or reviewing the drawing with an engineer from a different firm. You probably want to protect your intellectual property from being copied. You can easily restrict your collaborator from downloading the drawing – even if you granted him editing permissions. That’s an advantage Project Butterfly has over sending DWG files over e-mail – your collaborator does not retain a copy of the drawing after the collaboration has ended.

These days we are considering to add markup ability to the read-only permission, so that your collaborators can always add their input without messing with your geometry.

What do you think? Vote in the poll:

One Comment

  1. crAsh
    Posted March 31, 2010 at 7:17 PM | Permalink

    Ideally there should be options for both read-only and read-only with markups


Post a Comment

Required fields are marked *

*
*

%d bloggers like this: