This article provides answers for Enterprise users moving to InVision V7
We are currently rolling out the new V7 in stages. Users on a consumer plan will be updated to the V7 experience at the appropriate time.
Updating to InVision V7 lets you experience the completely new InVision—built to keep you and your team organized.
This guide provides key details about what to expect in V7:
- What’s new in V7 (and what you’ll still enjoy from V6)
- Things to prepare before updating from V6 to V7
- Account access, sharing rights, and document visibility
- Additional V7 resources
Before updating to V7, please be sure to carefully review these important prerequisites and information on feature availability.
What's new in InVision V7
The following are some of the new features that V7 users are loving.
New user roles
New user roles let you provide the right level of visibility to the right people. In V7, we’re introducing two new roles: members and guests.
Enterprise contributor and reviewer roles have been retired in V7; however, the permissions and intended limitations for these roles are still available, and users who had those roles in V6 will simply be assigned a new corresponding role in V7. Learn more.
Redesigned homepage
Quickly access documents, groups, design systems, and people settings via the new sidebar navigation.
Groups and Spaces
Available only in V7, groups are document folders that help you group and share designs across your team. They provide the access to work your team needs. You can add any document type to a group, and then create a space within a group to add a layer of organization, providing simple, yet powerful organization for your work.
By default Groups are public to all team members, but now in V7 they can be set to invite-only giving greater control over who can discover and access these groups—along with the documents within them. As a best practice, we recommend creating groups for each team or squad using InVision.
Groups was previously known as Spaces in InVision V6. Your V6 spaces will still be accessible after the update to V7, but they will be known as groups.
Upon conversion, visibility of your V7 groups depends on which roles in V6 were able to preview and join all company documents. If this setting was off for contributors, your V7 groups will be invite only. If this setting was on for either all roles, or all roles except reviewers, your V7 groups will be open to everyone.
Document permissions
New document permissions let you control who can access your documents. Within the share dialogue, you’ll notice a settings screen for each document. Here you determine who can open the document and which actions they can take.
Self-serve SSO and SCIM provisioning
InVision V7 Enterprise teams can directly manage SSO settings and set up SCIM provisioning without the need to contact InVision Support.
If your V6 Enterprise already has SSO set up, those settings will be migrated at the time of your update to V7. If your team runs into sign-in trouble after the update, please reach out to our Support team.
Currently, V7 works with any SAML 2.0 compliant SSO identity provider (IdP) and supports SCIM provisioning via Okta, OneLogin, or Azure.
Specs
Available only in V7, Specs are a new type of InVision document tailored for a specific job—design-to-development collaboration.
You can also inspect screens in Freehand. Learn more.
Screen Labels
Screen Labels let you create customizable filtered views and easily share links to each view. Manage existing labels or create new ones, like Jira milestones.
Your V6 workflow statuses will become screen labels after the update to V7.
Sets
Use Sets to organize your prototype screens into different sections. Sets are especially helpful for creating distinct flows or grouping by platform.
Your V6 screen sections will become sets after the update to V7.
Highlighted comments
If you can't be there to review a prototype with viewers, don't sweat it! Use Highlighted Comments as visual comment markers to grab viewers' attention and give context.
Your V6 tour points will become highlighted comments after the update to V7. Other types of comments will become regular comments.
Prototype screen history
The screen history feature in V7 lets you get daringly creative with your design collaboration—without the fear that wandering too far from previous design iterations might leave you lost with no way back.
Core capabilities
You’ll also still enjoy many of the core capabilities in the current version of InVision (V6), including these InVision staples:
- Craft Sync for sending Sketch and Photoshop designs into InVision instantly
- Prototypes for transforming static designs into clickable prototypes
- Freehand for capturing feedback throughout the product design process
- Boards for telling stories and sharing files
- Inspect for turning prototypes into design specs
- Public share links for making documents viewable to anyone who needs them
This release represents an initial set of capabilities that we’ll be continually adding to and evolving, so please let us know what works well, what doesn’t, and any ideas you may have on how to improve the overall experience.
Preparing for your InVision V7 update
It's important that you're fully aware of some things before deciding to embrace InVision V7, including a few things to prepare and consider before updating from V6 to V7 as well as the differences in available features.
InVision V7 prerequisites
Before updating to InVision V7, please read the following prerequisites and considerations:
- Consolidate all documents before Initial transition: As part of your Enterprise team’s transition to V7, we will move all of your members and company settings.
InVision cannot transfer documents from other accounts to your Enterprise account once we have moved it to V7; therefore, your V6 admin must have all people on the team consolidate their documents—including any from their personal V6 accounts that should have belonged to the Enterprise—prior to migrating your Enterprise to V7.
- Data created in InVision V7 is not backward compatible: After the transition, all of your V6 documents will be accessible on the new V7 platform.
- Access to documents: All of the prototypes, boards (not applicable to V6 Private Cloud users; see note below), and freehands your team created will be brought over to V7. If you haven't already moved your documents in V6 into a space, we recommend you do this to make finding documents in V7 seamless for your team. After the update, any documents that didn't already belong to a space in V6 will be placed in the Migrated Documents group in V7. This group is invite-only, but by default, anyone who had access to view all documents in V6 will have access to the Migrated Documents group in V7.
- Update from Legacy DSM: If you use Legacy DSM, you must update your legacy design systems to the New DSM before your update. Learn more here.
For InVision V6 Private Cloud users, Boards will not be brought over to their new InVision . Learn more here.
- IdP-Initiated SSO is not supported in InVision V7: If your company is using IdP-Initiated SSO, you will need to update your IdP configuration to an SP-initiated SSO before updating to V7. Download InVision’s SAML metadata from this URL: https://your_enterprise_subdomain.invisionapp.com/sso/metadata
- Updated Craft: For the best experience, please update to the latest version of Craft prior to the transition. Also review the note below in the feature availability bullet points.
-
Planned downtime: The transition will require planned downtime, so keep an eye out for email and in-app reminder messages once your Enterprise is scheduled. The transition requires around 2 hours on average and will be run during off-business hours, which are listed here in EST:
- 10pm - 7am, Monday through Thursday
- 8pm Friday - 8pm Sunday
- 7pm Sunday - 7am Monday
InVision V7 feature availability
Some InVision V6 features are not currently supported in V7 due to low usage:
- Tour Points within comments. Now called highlighted comments, this feature has been modified for additional flexibility in V7. You can use highlighted comments as tour guides, plus you can now select colors to establish comment categories that streamline communication.
- Workflow. You can now achieve similar results with screen labels in V7.
- Prototype Assets tab. You can achieve similar functionality by using Craft to export assets from Sketch so they appear in the Inspect Assets tab. Learn how to download existing assets before updating to V7.
- Duplicate boards and freehands.
- Starred documents.
- Activity (global and document-level).
- Custom branding for Enterprise teams.
- In InVision V7 prototypes, screens synced using Craft are updated based on the artboard ID instead of artboard name. Learn more here.
With InVision V7, you can export your prototype as a fully functioning offline prototype, ZIP file, or PDF—though it's not possible to use landscape orientation or use password protection when exporting to PDF.
Browser requirements for InVision V7
InVision V7 supports the latest 2 versions of the following browsers:
Reporting issues
If you’d like to share any feedback or report any issues with InVision V7, please contact InVision Support. Our team will work directly with you to ensure you have a smooth experience going forward, and your feedback will help us shape the future of the new V7 platform.
Getting set up in InVision V7
This guide provides instructions for a few common getting-started tasks and questions our Customer Success Managers often hear from people who have recently updated from InVision V6 to InVision V7.
For a complete walkthrough of how to configure and create your first documents in InVision V7, check out the rest of this V7 product documentation.
Signing in
Once you receive an email confirmation that the transition to InVision V7 is complete, you and your team members can access your new InVision V7 team account.
To sign in to InVision V7:
- Click login.invisionapp.com.
- Enter the email address and password for your Team or Enterprise account. These should be the same account credentials you used for InVision V6.
- Next to the team you want to use, click Select.
You also have the option to sign in to your team by navigating directly to your unique InVision team domain: your-team-name.invisionapp.com.
Team sharing settings
In InVision V7, you’ll find that the Let members invite people from within documents and groups setting is turned off by default. This is to prevent team members from unintentionally creating new paid Enterprise licenses by inviting new users to documents or groups.
If you’re an owner or admin of an InVision V7 team or Enterprise and would like to change this setting:
- Sign in to your InVision team or Enterprise here:
your-team-name.invisionapp.com - In the lower-left corner, click the expandable team tray.
- Click Settings, and then click Team sharing settings.
- Uncheck the toggle and click Update.
Document visibility
If you updated from InVision V6 to V7, you may notice a group called Migrated Documents. This group is invite-only, but by default, anyone who had access to view all documents in InVision V6 will have access to the Migrated Documents group in InVision V7. To learn more, check out this article: InVision V7: What is the Migrated Documents group?
Consider creating groups to ensure stakeholders maintain access to project-specific and/or team documents moving forward. For more information, check out the following articles on the Groups feature:
- InVision V7: How do I transfer my document to another group?
- InVision V7: How do I add people to a group?
User groups
When updating to the new InVision, any teams you created in V6 will be converted to user groups. User groups allow you to more easily manage document access for a large number of users.
It's important to note that there's a difference in permissions for V6 teams and V7 user groups. To learn how this difference can impact your groups, check out this article on converting teams to groups.
The more you know
We’re here for you every step of the way! In addition to the rest of this product documentation, lean on these resources to level up your InVision V7 know-how.
