# Guide to your first evolve ### 1. Account Access * **Receive Admin Credentials:** The gospace AI team will provision your admin account and email you a login link (e.g. ). Follow the link to set your password and access the admin console. * **Assign Roles:** If needed, assign additional admin users or roles in **Admin > Roles** so the appropriate team members have access. [Roles](/admin/admin/roles.md) ### 2. Create Locations & Upload Floorplans * **Add a Location:** In the admin portal, open **Locations** and click **+ Add Location**. Enter the location **Name** and **Address** (you can search to auto-fill, then click **Confirm Address** to validate) [docs.gospace.com](https://docs.gospace.com/admin/get-started/create-a-location#:~:text=%E2%96%AA%20Name%3A%20Enter%20the%20name,for%20different%20locations%20created%20here). * **Publish Location:** After entering details, click **Review Changes** (top bar) and then **Publish** to activate the location [docs.gospace.com](https://docs.gospace.com/admin/get-started/create-a-location#:~:text=Once%20you%20add%20a%20location%2C,You%20must). The location will now appear in the list of active locations. * **IF you don't already have a CAD file** of your floorplan. Send floorplans to gospace AI in any format (including pptx, pdf) to be auto-generated into a .DXF via our floorplan generator. This can take 24-7 hours. gospace will reach out once the floorplan(s) have been generated. * **Add Floor (Layer):** Still under that location, click **+ Add Layer** (or Floor) and upload the floorplan file (e.g. a .DXF) for that level. Uploading the floorplan will automatically create zones, rooms, and workpoints on that floor [docs.gospace.com](https://docs.gospace.com/whats-new/release-notes/v2.0.0-beta#:~:text=,floor%20plan%20editor%20in%20planning). * For the DXF, we need the following layers: * workpoints * wall\_perimeters * Optional: clusters * Optional: wall\_partitions * Optional: zones * Optional: areas * Optional: rooms * **Configure the Floorplan:** Use the **Floorplan Editor** (under **Workplace > Space Settings > Floorplan**) to review/edit the generated layout. You can add zones, add labels to spaces, for example "Focus Pods". This ensures your office is accurate before allocations begin. ### 3. Directory Integration * **Choose Integration Type:** In **Integrations**, select your directory sync method. gospace supports SFTP (CSV import), Microsoft Azure AD, or Snowflake [docs.gospace.com](https://docs.gospace.com/integrations/overview#:~:text=,of%20user%20and%20team%20data). * **SFTP (CSV):** Select **SFTP – user management**. Enter your SFTP server’s Host, Port, and login credentials. (This should point to a folder of user/team CSV files.) [SFTP](/integrations/connecting-an-integration/sftp.md) * **Snowflake:** Select **Snowflake – user management**. Enter your Snowflake **Account Name** (`.` format), **Role** (e.g. `ACCOUNTADMIN`), and credentials [docs.gospace.com](https://docs.gospace.com/integrations/connect-your-integration/snowflake#:~:text=Role). This connects to your Snowflake database to import user/team tables. * **Microsoft AD:** Select **Microsoft Active Directory – user management**. In Azure, create or use an App Registration to get the **Client ID**, **Client Secret**, and **Tenant ID**. Paste these into gospace (under Azure AD App’s Certificates & Secrets) [docs.gospace.com](https://docs.gospace.com/integrations/connect-your-integration/microsoft-ad#:~:text=When%20it%20comes%20to%20getting,under%20the%20App%20Registration%27s%20blade). gospace will connect to Microsoft 365/Azure AD to import users. * **Map Directory Fields:** After connecting, you’ll map CSV/AD fields to gospace user/team fields: * **Users:** Map your columns (from CSV or AD attributes) to *User ID*, *Email*, *First Name*, *Last Name* [docs.gospace.com](https://docs.gospace.com/integrations/map-your-directory/users#:~:text=%2A%20,uniquely%20identify%20users%20in%20gospace). These are mandatory fields. Optionally map *Active Start/End Date* or *Occupancy Mapping ID* if used. * **Teams:** Map your columns to *Team ID* and *Team Name* [docs.gospace.com](https://docs.gospace.com/integrations/map-your-directory/teams#:~:text=,format%20used%20in%20your%20organisation). (Optional: map *Allow Guests* or other team properties as needed.) * **Custom Mappings/Filters:** Use the custom mappings section to set default locations or priorities (e.g., map a “Default Location” column to a user’s home office). Apply filters if you only want a subset of users/teams. * **Confirm and Import:** Review the mappings carefully. Click **Confirm** to save the configuration and run an initial import [docs.gospace.com](https://docs.gospace.com/integrations/map-your-directory/users#:~:text=Once%20you%27ve%20completed%20your%20user,apply%20your%20user%20mapping%20settings). gospace will now sync users and teams (for SFTP/Snowflake it will update nightly) and create them in the system, automatically removing leavers. ### 4. Historic Occupancy Integration * **Import Past Attendance (Optional):** If you have historical occupancy/attendance logs (e.g. past check-ins), import them similarly. In **Integrations**, choose **SFTP – location occupancy data** or **Snowflake – location occupancy data** to point to your past data, and instead select the **"Historic Occupancy"** radio button. * **Map Occupancy Fields:** On the mapping screen, set the *Person ID* field to match the *Person ID* you used when importing users [docs.gospace.com](https://docs.gospace.com/integrations/how-to-map-your-occupancy-data#:~:text=This%20needs%20to%20be%20the,occupancy%20records%20to%20your%20users). This links each attendance record to the correct user in gospace. Also map the occupancy *Location* column so that each record’s location value matches a gospace Location. * **Finalise Import:** Confirm the mapping and run the import. This loads historical occupancy into gospace and trains AIDRA on past attendance patterns, we recommend at least 3 weeks of historic data, **and ideally 12 months**, these can be uploaded in one file as long as the date/time field is properly defined when mapping. ### 5. Real-Time Occupancy Integration * **Choose a Live Data Source:** gospace supports real-time occupancy feeds from Cisco Meraki, Snowflake, or SFTP [docs.gospace.com](https://docs.gospace.com/whats-new/release-notes/v2.0.0-beta#:~:text=,allocating%20space%20to%20your%20users). Configure at least one for ongoing presence data. * **Cisco Meraki:** Select **Meraki – location occupancy data**. Enter your **Organization ID** and **Network ID** (obtain these from the Meraki dashboard via the API calls: e.g. `GET /api/v0/organizations` and `/networks`) and your **API Key** [docs.gospace.com](https://docs.gospace.com/integrations/connect-your-integration/cisco-meraki#:~:text=To%20retrieve%20your%20organisation%20ID%3A)[docs.gospace.com](https://docs.gospace.com/integrations/connect-your-integration/cisco-meraki#:~:text=,the%20Cisco%20Meraki%20Dashboard%20API%E2%80%9D). Enable Meraki API access in your Meraki organization, then click **Continue** to test and activate. This will stream live Wi-Fi/Presence data into gospace. * **Snowflake:** Select **Snowflake – location occupancy data** and enter your account details (same Snowflake account, role, credentials) [docs.gospace.com](https://docs.gospace.com/integrations/connect-your-integration/snowflake#:~:text=To%20begin%2C%20click%20on%20either,You%27ll%20then%20see%20the%20below). gospace will poll a designated Snowflake table for check-in data each day. * **SFTP:** Select **SFTP – location occupancy data** and provide your SFTP credentials, pointing to attendance CSVs. * **Map Real-Time Fields:** As before, map the *Person ID* to your user IDs and the *Location* field to gospace Locations (see **Step 4**). Confirm the integration. gospace will now ingest live occupancy data daily to refine its forecasts. ### 6. Microsoft SSO Setup * **Verify Your Domain:** In **Admin > Domain Verification**, add and verify your organization’s email domain (e.g. **example.com**) by following the instructions (typically adding a DNS TXT record) [docs.gospace.com](https://docs.gospace.com/whats-new/release-notes/v2.0.0-beta#:~:text=,end%20experience). Verification is required before enabling SSO. * **Enable SSO:** Go to **Integrations > SSO**. For **Microsoft SSO**, enter your verified domain and the Azure AD App’s Client ID and Secret (the same values used for the directory integration). Enable the integration so that gospace redirects logins to Azure AD. (Support for Okta/Google SSO will be added later.) Once configured, all users in your domain can log into gospace with single sign-on [docs.gospace.com](https://docs.gospace.com/whats-new/release-notes/v2.0.0-beta#:~:text=,end%20experience). ### 7. Features that need enabling for a simulation * **Navigate to locations > select the location < settings**. For a simulation ensure the following features are enabled/disabled:
### 8. Features that need enabling for a live configuration * **Navigate to locations > select the location < settings**. For a live building ensure the following features are enabled/disabled:
Similarly, when you're ready to onboard users via ensure notifications are enabled via:
### 9. Wait 24 hours and time to evolve! * **Navigate to workplace > select the location < allocations**. As long as you have uploaded enough historic data for Aidra to learn (otherwise please wait up to 2 weeks), then click optimise you will begin to see allocations being created by the AI based on your user/team forecasting.
--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.gospace.com/admin/guides/guide-to-your-first-evolve.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.