A User is someone with a Visor account. When someone is invited to view, comment on, or edit a Workbooks, they become a User within a Workspace. Users can belong to multiple Workspaces.
A Workspace is a collection of Workbooks and the Users who have access to them. In order to access any of the Workbooks within a Workspace, the User must be a member of that Workspace and have at least Viewer-level access to the Workbook.
You can view all of the Workbooks that you have access to within your current Workspace here: https://app.visor.us/sheets
Users can set up as many Workspaces as they like. To switch between Workspaces or add a new Workspace, log in and then visit https:/app.visor.us/start.
A Workbook is effectively a "file" of data within Visor that can be displayed and formatted in different ways (see Views). Each Workbook can contain multiple Folders, and each Folder can contain multiple Views. There is no limit to the number of users who can view or edit a Workbook, but a Workbook can only belong to one Workspace.
Users will find a list of all the Workbooks they have access to on the Visor homepage.
Views are the ways in which the data in a Workbook are displayed and are accessible through tabs at the bottom of a Workbook. There are currently three types of Views in Visor: Table, Gantt, and Timeline. Users can switch between Views or add new Views within a Workbook by using the tabs at the bottom of the window.
Records represent the main items in a Workbook. In Table View and Gantt View, Records are shown as rows. In Timeline View, Records are shown as tiles that Users can drag.
Jira Users typically have only one Issue linked per Record. In this case, Records can be thought of as the equivalent of Issues in Jira.
However, it is also possible for each Record to link to multiple different items from other Connected Apps. For example, a Record can link to both a Jira Issue as well as a Salesforce Contact, creating a custom relationship between data from multiple Connected Apps.
Users are also able to Nest their Records for easier data organization. See Nesting for more information.
Fields are the attributes of a Record, and are displayed as columns in Table View and Gantt View. Fields can also be seen in the pop up that appears when clicking on the tiles in Gantt View and Timeline View.
In Gantt View, Users can select the Fields they'd like to appear on the Gantt chart. While the Primary Label Field controls how the Records are plotted in Gantt View, Users can also include additional Fields to be displayed to the right of the Primary Label Field.
Timeline View has a special Field called Swimlane Field. This Field, combined with Start Date and End Date Fields are how Visor plots the Records on a Timeline.
To add a new Field in Table View and Gantt View, scroll the Fields all the way to the right and click the "Add Field" link at the top. (It is not possible to add additional Custom Fields from Timeline View at this time. )
A Custom Field is a Field that contains an attribute of a Records, but that attribute can only be saved in Visor (unlike Connected Fields, which sync back to Connected Apps).
Visor supports the following Custom Field types: Plain Text, Dropdown, Date, Date/Time, Time, and Number.
Connected Fields contain data in Visor that is able to Sync with a Connected App. Connected Fields will be editable in Visor if the Connected App it came from supports editing.
As Users edit Connected Fields in Visor, those changes will be saved in Visor for the next sync. A yellow indicator will appear on edited cells that have not yet synced. Once a Sync occurs, the yellow indicator will disappear.
Nesting is an option that Users have when Importing Jira Issues to Visor. Users are able to apply the same hierarchy that existed between Issues in Jira to newly imported Records in Visor. There is no limit to how many levels of Nesting a User can apply to their Records.
If a User does not elect to Nest their Jira Issues, all Jira issues types will be imported to Visor as Records. Users can always Nest records in a Workbook manually, even if Nesting was not selected during an import.
In Table View and Gantt View, arrows will appear next to any nested Records in the Primary Label Field. Users can click these arrows to either display or hide that Parent Record's lower, nested Records.
Nested Records are not displayed on the Timeline in Timeline View, however, Users can see if a Record belongs to a Parent Record by clicking on the tile and reviewing its Parent Field attributes.
The Parent Field is a special Field that appears automatically after Nesting is established in a Workbook, and it indicates which Record is the parent of any Nested Record.
The Parent Field cannot be deleted once Nesting has been established within a Workbook, and there is no way to add the Parent Field without first establishing Nesting.
See Nesting for more information.
The Connection Field is the Field where Users can link to records in a Connected App. Each Connection in Visor has exactly one Connection Field. For Connected Apps and external record types that support searching, Users can search for external records by name. Selecting one of the choices will link that Visor Record to that external Record. Once that happens, Visor will pull data into the associated Connected Fields in that Record.
Primary Label Field
The Primary Label Field is the Field that will be used to represent the name of a Record. There can only be one Primary Label Field at a time, and the value in the Primary Label Field will be used when displaying the Records in Gantt View and Timeline View. and Card view.
Users cannot delete or hide the Primary Label Field. However, it can be renamed, or the Primary Label Field designation can be changed to a different Field.
To change which Field is the Primary Label, click the header row in of the first column in Table view and select the option: "Change Primary Label."
Integration refers to the relationship between Visor and a Connected App that is authorized to sync with Visor. Users are able to integrate multiple Connected Apps to their Workspace. Examples of available app integrations include Jira, Salesforce, HubSpot.
To see which Integrations are active, visit: https://app.visor.us/settings/integrations
A Sync is an operation that allows users to update their data in both a Visor Workbook and a Connected App. A Sync may be used to update existing Records, import new ones, and/or Refresh the Field configuration.
Visor's Syncing capabilities are second to none. Currently, Visor is the only product on the market that offers bi-directional Syncing. Other products are only able to pull data in.
Visor's Syncing is smart. As a User makes changes to their Workbook, Visor keeps track of which pieces of data were changed. When it comes time for a Sync, Visor pushes only the changed data (in technical terms, the delta) to the Connected App — and nothing else.
Next, Visor pulls down the freshest data from the Connected App. In arranging Visor's Syncs in this specific order (push first, then pull), Visor is able to double check that the changes it just pushed were pushed properly. Visor compares the most recent value in the Connected App with the value that it receives when pulling from the Connected App.
In the event that any differing values are found, a warning message appears in the Workbook. Visor most often finds differing values if the Connected App changes minor formatting like capitalization or spacing.
A sync credit is our unit of measuring your usage within Visor. The following count as sync credits:
- 1 credit per cell changed & pushed to another app
- 1 credit per Record (row) imported or linked
- 1 credit per pull per Record (either during a sync or when a synced field is added and needs to be filled with data)
- 1 credit per Field Refresh
When you run out of Sync Credits, we won't cut you off immediately. We want to make sure your syncs can keep running and you can keep your data intact. A member of our Customer Success team will reach out about getting you more credits, and we'll give a 7-day grace period before preventing you from using more credits.
Linked Records are an innovation that is unique to Visor, where a cell in a Visor Workbook links to another external record in a Connected App. Once the Visor Cell and external record are linked, the corresponding Connected Fields will push and pull data.
When records are linked to Visor, the Connected Fields will be automatically filled with the relevant data for that linked Record. For example, let's say a User links a Jira Issue. Any of the Connected Fields related to that Connection will be populated with the data from Jira. Any changes a User makes in Visor will be staged, and eventually Synced back to Jira. (see section on syncing)
Currently, Visor supports Linking Records by searching for external records by name. For example, Users can search Visor for Jira Issues by name. They can also search directly by the issue key if they prefer.
If a Record is not already searchable in Salesforce, it will not be compatible with Visor's linking system and cannot be searched in Visor.
A Cell is a specific unit of data at the intersection of a Record and a Field.
An Import is the act of pulling data into Visor from a Connected App.
Connected App is generic term that is used to refer to products like Jira, Salesforce or HubSpot. It doesn't imply anything about a relationship between one of these apps and Visor. (Meaning, Jira is still considered a Connected App, even if there is no Jira data in a given User's Workbook.) The term can also be used to refer to integrations we plan on building in the future (like Asana).
A Connection is the fundamental unit of connectivity between a Visor Workbook and data from a Connected App. It refers to a Connection Field and its associated Connected Fields.
Users don't run a Sync with Jira, they run a sync on the Connection. Users may have multiple Connections to a Connected App, and they can run a Sync on only one specific connection (meaning the Connected Fields associated with that Connection). It is also possible to run a Sync for the entirety of a Connected App's Connections, but the smallest possible unit of a Sync is the Connection itself.
Two Way Sync
A Two Way Sync is a Sync that either takes updated information from a Connected App and updates the data in Visor, or vice versa.
One Way Sync
A One Way Sync is a Sync that pulls information from a Connected App into Visor (and not the other way around).
Conditional Formatting is the ability to color-code and format the text of any dropdown Fields. Conditional Formatting also allows users to Filter by the dropdown Fields within a Workbook, effectively allowing Users to "hide" extraneous data depending on the audience for that View.
Timeline View organizes data into a visual layout based on the start and end dates in each Record and the designated Swimlane Field.
All Records that are displayed in Timeline View are synced to data in other Views, so as changes are made in Timeline View, those changes will also be displayed in Table View and Gantt View as well.
Timeline View also supports Connected App Fields, so any changes made in Visor's Timeline View can be synchronized back to a Connected App with a single click.
Gantt View organizes data into a visual layout based on the Primary Label Field, as well as start date and end date. Records are displayed as tiles, and Users can edit start date and end date Fields by clicking and dragging the tiles on the graph.
Unlike in Timeline View (which only displays the Primary Swimlane Field), Gantt View can display multiple Fields in addition to the Primary Label Field.
All Records that are displayed in Gantt View are synced to data in other Views, so as changes are made in Gantt View, those changes will also be displayed in Table View and Timeline View as well.
Table View organizes data into sets of rows (Records) and columns (Fields). This View is most similar to a traditional spreadsheet, but with a few key Product Management-specific capabilities. Any Conditional Formatting that a User applies to the Fields in Table View will also appear in Gantt View and Timeline View.
All Records that are displayed in Table View are synced to data in other Views, so as changes are made in Table View, those changes will also be displayed in Gantt View and Timeline View as well.
A Swimlane is a row on the Timeline in Timeline View that corresponds to one of the Swimlane Field's values.
For example, let's say a User selects the Assignee Field to be her Swimlane Field, and she has 5 Assignees in to select from in her Workbook. In this example, her Timeline View will have 5 rows in which various Records could be plotted. Each of those 5 rows are called Swimlanes.
The Swimlane Field is one of the 3 Fields used to plot Records in Timeline View. (The other two Fields used are Start Date and End Date.)
Users can change which Field has the Swimlane Field designation by clicking in the header row of the first column in Timeline View. However, the Swimlane Field is only compatible with Fields in a Workbook that have a finite and knowable set of options. (For example, Jira's Assignee Field.)
Here's how the 3 Fields are used to plot records in Timeline View:
- The value in the Record's Swimlane Field determines which Swimlane Record is placed in.
- The value in the Record's Start Date Field determines the left edge of the Record.
- The value in the Record's End Date Field determines the right edge of the Record.
Any Records that do not have a (valid) value in the Assignee Field will not be plotted on the Timeline, nor will Records that have an End Date that occurs before the Start Date. Please note that there is currently no way to see Records that do not have Assignees in Timeline View at this time.
A Field Refresh is how Visor learns about your Connected Apps record types and fields. This then makes them available to be selected for a Connection in Visor. During a Field Refresh, Visor also learns about the Fields associated with Record types. This is how Visor learns what dropdown choices to show for dropdown fields. It's also how Visor learns about other field behaviors, like maximum lengths.
A Field Refresh updates the configuration of a given Field in Visor to best match the configuration of that field in the Connected App. For example, If a Salesforce Admin increased the character limit of a field from 125 characters to 250 in Salesforce, a Field Refresh would need to be conducted in Visor to increase the character limit of the corresponding Visor Field as well.
Users do not need to Refresh Fields frequently— only if a lot of changes have been made in the Connected Apps. Users can Refresh one Field per Connected App per time.
Please keep in mind that Field Refreshes are not instantaneous, and the time it takes to complete the process will vary. Refreshing a Jira Field can take anywhere from 10-15 seconds, and the time it takes to Refresh a Salesforce Field can vary even more (depending on how many objects are being mapped). As Visor is exposed to more Salesforce Record types, the time to complete a Field Refresh could be 50 seconds or more.
The name of a field in Visor which can be seen at the top of a column.
Visor supports a number of different user roles (currently: Owner, Editor, Commenter, and Viewer). To see what each permissions level provides access to, see our Sharing & Permissions page. To see what permissions levels your account has access to, see our Pricing Page.
Ready to try this in Visor?
Written by Victoria
Updated this week