We’ve got the answers
Let us know how we can help you get the most out of GRID.
Frequently asked questions
Almost, but not completely. Certain functions of common spreadsheet software are not available in GRID. These are mostly highly specialized functions or functions that are rarely used. Most notably GRID does not implement scripting languages such as Visual Basic for Applications (VBA) or App Script. Overall - however - 98% of all spreadsheets are fully supported by GRID, and for most of the rest there are relatively simple workarounds to provide the same results.
GRID supports spreadsheet files from Microsoft Excel™ (xlsx), Google Sheets™ and flat CSV data files. Users can link to these files in cloud drives such as Dropbox, OneDrive or Google Drive; provide a URL to the files; or upload them directly from their own computer.
This is a great question, and the answer is no. GRID does not write back into your original spreadsheet when a GRID document is interacted with or altered. Just think of your GRID document as a protective layer between your spreadsheet and your viewers. You decide which parts of the spreadsheet you want to present, how you want it to appear, and who will see it. The spreadsheets you’ve connected to GRID will never be altered by changes made (by author or viewers) to the GRID document.
You can embed GRID charts in multiple platforms through such as Airtable, Confluence, ClickUp, Monday.com, Medium, and Lucid. And you can use Notion GRID’s Link Preview integration to embed charts into your Notion workspace.
GRID Sheets is our in-built spreadsheet editor. Using GRID Sheets is perfect for when you're either starting your project from scratch or if you want to manipulate and combine data from other data sources such as spreadsheets, Notion databases, and Airtable bases.
No, GRID Sheets are an integral part of GRID documents, and therefore, all GRID documents will have a GRID Sheet as the first data source in the data panel. This enables you to use the GRID Sheet to do your calculations in GRID and easily combine data from different sources.
To start collaborating on a GRID document, create a User Group. Once you’ve added colleagues to the group, group members will be able to start Conversations and leave replies for everyone to see. You’ll be able to keep feedback contextual and gather valuable ideas right in your doc.
Currently, GRID does not support co-authoring of documents. For now, each document has one author/owner.
We’re not currently able to offer a document-building service, but we’d still love to help you get started. Drop us a line at [email protected] and we can schedule a short call! We’ll assist you with the basics so that you can easily create GRID documents yourself in no time at all.
If you’d prefer assistance via email, let us know what you’d like to achieve and we’ll guide you through the steps that best work for your case.
With our Professional plan, you unlock custom colors and fonts for your documents, access to document statistics, and the option to remove GRID's watermark when you embed your charts or entire docs. Check out the Pricing page for a full list of Pro features.
Our Pro plan includes one, individual account. Upgrading to the Teams plan will unlock unlimited seats per company email domain, so you can take your entire team to the next level. See more about our Teams plan here.
The contents of the underlying spreadsheet are sent to a viewer’s browser when loading a GRID document. While this is not the spreadsheet file itself, this might allow a technically skilled person to reconstruct the spreadsheet model with some effort.
Data is stored in AWS in eu-west-1 (Ireland) AWS has a public SOC 3 report on Security, Availability & Confidentiality (pdf)
The bulk of the data is stored in AWS RDS. Amazon RDS encryption is used to secure DB instances and snapshots at rest. Amazon RDS encryption uses the industry standard AES-256 encryption algorithm. Volatile data is stored in AWS Elasticache. Data and snapshots are encrypted at rest.
GRID is not a data controller for any personal data relating to other individuals that might be included in the work you upload to our systems. You or your company will be the data controller in such instances and GRID will be a data processor. If you decide to publish any personal data, you have to understand that you are responsible and need to make sure that publishing such personal data is lawful.
Currently we do not offer any on-premise options and we do not plan to do so in the foreseeable future.
GRID is suitable for small to medium sized companies and IT independent groups within larger organizations.
GRID takes a serious approach to protecting our users and their data. First, we use industry-standard methods such as TLS and end-to-end encryption for all communications and data centers with acknowledged certifications. All user data is encrypted at rest to prevent any compromises in case of stolen hardware.
We have a private bug bounty program managed by Intigriti where we continually leverage their community of more than 70,000 security professionals to probe for weaknesses in our product. We engage in regular penetration tests where a select group of their researchers is tasked with probing the product and given extra information about system architecture to increase the chance of them finding weaknesses. This provides our engineers with information about security issues from trusted sources which are contractually bound to report and secrecy, allowing us to find and fix any issues before they are exploited. When vulnerabilities in existing features are reported, we treat them as a possible breach and initiate our internal breach review process.
Finally, we use CloudFlare to protect against denial of service attacks and many types of suspicious/malicious requests and to give us added ability to block out traffic from harmful actors.
If we detect or suspect a breach in our systems, we initiate an internal process to map the breach and gauge its scope and severity.
The process stipulates that, in compliance with the GDPR, we first determine whether personal data has been affected, so we can alert supervisory authorities within 72 hours. Once the scope of the breach has been determined, we will contact the affected users and share with them exactly which documents and data sources of theirs may have been affected and what we have done to mitigate the issue. Internally we conduct post-mortems to analyze the whole context leading up to an incident to identify any measures we can take to prevent such scenarios. If pertinent, we will publish these so our users may better understand what measures are being taken and whether they meet their requirements.
GRID is not a data controller for any personal data relating to other individuals that might be included in the work you upload to our systems. You or your company will be the data controller in such instances, and GRID will be a data processor. If you decide to publish any personal data, you have to understand that you are responsible and need to make sure that publishing such personal data is lawful.