Security
Bring the requirement. A build for your organization is where we meet it. This page does not say we already hold a certification.
The account you open today
Sign-in is an email code. That service runs on Cloudflare. Plans you open there are stored with Forward Layout. Operators of that environment can access them to support the product. We do not use plan images for model training.
You can ask us to delete that data. You can ask for a signed DPA before a commercial set goes there. Prefer a sample or a redacted set until the build is running for you, or until that agreement is signed.
A build
A build for your organization is isolated for you. On your network, you open plans on your computers and sync stays on your servers. If we host it, sync stays in the environment that is only yours.
You run the build. You do not own the software. SSO, your directory, and a managed install are part of that work. They are not settings on the account you open today.
What a review asks
Tell us the requirement. We work with you to meet it on the build. The topics below are the ones a review usually names. Naming them here is not a claim that a report, a badge, or a finished vendor packet already exists.
Isolation. Where the environment runs, including data residency. SSO and your directory (SAML, OIDC, SCIM, if that is what you require). A DPA. Encryption in transit and at rest. Who at Forward Layout can see files, and how that access is limited on a build. A managed install for Mac and Windows. A report such as SOC 2, or a pen test, if your review requires one.
Access and administrative changes on today's service are on an append-only audit log an organization admin can read, kept for 365 days. Sign-in, invites, role changes, and document and Project actions are on that log. A measurement on the sheet stays on the Project.
Who can open a Project
People and teams get View, Comment, Edit, or Full control on the Projects they should see (Project access). A guest can open one Project without joining the company directory. Revoke access when the bid is over.
Contact us
Email [email protected]. Send the requirements your review asks for, and where the files have to live. The build is an organization build. The company account is an Organization.
If you want to use the software now, sign in. That account syncs with Forward Layout. It is not your server.
Questions
- Are you SOC 2 certified?
- No. If your review requires SOC 2, a pen test, or another report, say so. We work with you to meet that requirement on a build. This page is not a certification.
- Where do files go if we sign in today?
- They sync with Forward Layout, on Cloudflare. Operators of that environment can access stored plans to support the product. A build is where sync stays on your servers, or in an environment that is only yours.
- Can we use our own sign-in?
- On a build, yes. SSO and your directory are part of that work. The account you open today uses an email code.
- Is every measurement on the audit log?
- No. The log covers access and administration, kept for 365 days. A length or a count on the sheet stays on the Project.
- Who should write?
- The person who owns the review, with the person who owns how the team works. Email [email protected] with the requirements and where the files have to live. The build note is Enterprise.