{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is a team in Forest?","acceptedAnswer":{"@type":"Answer","text":"A group of users with its own layout: pages, workflows, inbox, dashboards, visible actions and record views. Users and service accounts can belong to one or more teams."}},{"@type":"Question","name":"How do I build a page for my team?","acceptedAnswer":{"@type":"Answer","text":"Add a page, drag a collection and choose its segment, add the fields to display, then the actions operators need next to the data. Most pages need no code."}},{"@type":"Question","name":"Can each team see different records?","acceptedAnswer":{"@type":"Answer","text":"Yes. Combine teams with scopes so users see only the rows tied to their team, for example one country or one product line."}},{"@type":"Question","name":"How do I set up a new team quickly?","acceptedAnswer":{"@type":"Answer","text":"Create it from another team's layout, or copy one page from team to team. Engineers can also copy layouts with the Forest CLI."}},{"@type":"Question","name":"Can outsourced teams work in Forest?","acceptedAnswer":{"@type":"Answer","text":"Yes. Give them their own team, layout and scope, under a role that limits what they can do. Their activity is logged like any operator's."}},{"@type":"Question","name":"How do you ensure customer data never leaves our environment?","acceptedAnswer":{"@type":"Answer","text":"The Forest back-end runs inside your infrastructure, alongside your databases. Customer data travels to a provider only at the point where its service is called, and the response is logged back to the case. Data stays in your systems of record."}}]}