Inside Goliath an Overview of the Settings Integrations and Profile Configurations

GoliathData is a comprehensive real estate data and analytics platform designed to help professionals manage property information, market analysis, and client relationships through a unified dashboard. Understanding the Settings, Integrations, and Profile Configurations is essential for maximizing the platform's value and tailoring it to your specific workflow, team structure, and data sources.

TL;DR

• GoliathData's Settings panel controls user permissions, data preferences, and account-level configurations that affect how the entire team accesses and uses the platform.

• Integrations connect GoliathData to external tools (CRM systems, email platforms, MLS feeds, third-party analytics) to automate data flow and reduce manual entry.

• Profile Configurations allow individual users to customize their dashboard views, notification preferences, and personal data settings while maintaining compliance with team-wide policies.

Understanding the Settings Structure

The Settings area in GoliathData is organized into several distinct sections that control different aspects of your account and data management. At the account level, administrators can define company information, branding preferences, and fundamental data governance rules that apply across all users. These foundational settings ensure consistency in how property data is stored, reported, and shared within your organization.

User and team management settings allow you to add, remove, and assign roles to team members. Different role types typically include administrator (full platform access and settings control), manager (limited administrative abilities over assigned team members), agent (standard access to properties and clients), and viewer (read-only access for specific reports or properties). Defining these roles clearly prevents accidental data changes and maintains the principle of least privilege for security.

Data settings control how GoliathData handles property records, client information, and historical data. You can configure data retention policies, determine which fields are required for property entries, set up custom fields unique to your business, and establish validation rules that prevent incomplete or inconsistent data from entering your system. These controls are critical for maintaining data quality across your database.

Navigating Integration Options

GoliathData integrations fall into several categories based on the functions they support. MLS (Multiple Listing Service) integrations are foundational for real estate professionals, enabling automated import of active listings, sold data, and market statistics directly into your GoliathData dashboard. Rather than manually entering property details, integration with your regional MLS keeps your data current without manual effort.

CRM integrations connect GoliathData with customer relationship management platforms like HubSpot, Salesforce, or other real estate-specific systems. These bidirectional connections synchronize client contact information, interaction history, and deal stage data. When a property record is updated in GoliathData, those changes can automatically flow to your CRM, and vice versa, eliminating duplicate data entry and ensuring all systems reflect the current state of your business.

Email and communication integrations link your primary email platform to GoliathData, allowing you to log emails, create tasks from messages, and track client communications without leaving the platform. This reduces context-switching and ensures that important conversations are tied to the correct property records and client profiles. Some integrations support email-to-task automation, where incoming emails trigger specific workflows.

Financial and accounting integrations connect to platforms like QuickBooks or custom accounting systems, automating the flow of transaction data, commission records, and financial reports. Real estate teams managing multiple properties and transactions benefit significantly from this automation, as financial reconciliation becomes faster and errors decrease.

Analytics and reporting integrations pull data from third-party analytics tools or push GoliathData metrics to business intelligence platforms like Tableau, Power BI, or Google Analytics. These connections enable sophisticated reporting beyond what GoliathData's native reporting offers, and help you combine real estate data with other business metrics for comprehensive dashboards.

API integrations and webhooks allow developers to build custom connections or automate workflows between GoliathData and proprietary internal systems. If your organization has legacy systems or specialized tools, API access enables you to move data between them programmatically without manual intervention.

Setting Up and Configuring Integrations

Before enabling any integration, verify that you have the necessary credentials and permissions in the external system. For MLS integrations, you will typically need your MLS board credentials and account setup on their platform. For CRM systems, administrative access to that platform is required to authorize GoliathData as a trusted application.

Once you initiate an integration in GoliathData's Settings, you will be directed through an authentication flow. Most modern integrations use OAuth 2.0 or similar secure authentication protocols, so you authorize GoliathData without sharing passwords. Read the requested permissions carefully, as GoliathData will specify exactly what data it intends to access and modify.

After authentication succeeds, configure the synchronization parameters. Decide which data fields map between systems, how often updates should sync (real-time, hourly, daily), and which direction data flows (GoliathData to external system, external system to GoliathData, or bidirectional). Some integrations allow you to filter which records synchronize, so you can exclude test data or separate accounts.

Test the integration with a small subset of data before enabling it for your entire operation. Verify that property records sync correctly, that client information appears accurately in both systems, and that updates in one platform reflect promptly in the other. Document any field mapping decisions or special rules you establish, as you may need to refer to them during troubleshooting.

Profile Configurations and User Customization

Individual user profiles in GoliathData allow each team member to customize their experience while respecting account-wide policies and permissions. A user's profile includes their name, email, phone number, role, and permissions assigned by administrators. The profile section also stores authentication methods, allowing users to enable two-factor authentication, manage API keys, and control session timeouts for security.

Dashboard customization is a key feature of profile configuration. Users can choose which widgets appear on their home screen, reorder them, and configure what data each widget displays. An agent focused on new listings might prioritize a widget showing recent MLS additions in their territory, while a team manager might prefer a widget showing team performance metrics and closing statistics.

Notification settings allow users to control how they receive alerts about property changes, client actions, task assignments, and system events. Users can choose notification channels (in-app, email, SMS, push notification on mobile), frequency (real-time, daily digest, weekly summary), and filter which types of events trigger notifications. Customizing these prevents notification fatigue while ensuring critical alerts still reach the right people.

View and report preferences let users save custom filters and report templates for frequent use. Instead of rebuilding a market analysis report every week, a user can save their preferred parameters (geographic area, price range, property type, timeline) and rerun the same report with one click. These saved configurations increase efficiency and consistency in your analysis.

Search and data display preferences control how information appears to individual users. Users can set default sort order for property lists, choose which columns appear in data tables, configure default map views, and set preferences for how data is grouped or filtered. These customizations make the interface feel intuitive for each user's specific role and workflow.

Privacy and data access settings within profile configuration determine which properties and clients a user can see. Administrators set baseline permissions (an agent can see all properties they listed plus any assigned to them), but users can be granted additional read-only access to properties or clients as needed for collaboration. Users can also configure whether their own contact information is visible to other team members.

Security Considerations in Settings and Integrations

When configuring integrations, prioritize security by limiting integration permissions to the minimum required for functionality. If an integration only needs read access to property data, deny write permissions. Review integration permissions periodically, especially when integration partners update their services or when your team changes processes.

For user profile configurations, ensure that password policies are enforced account-wide. Administrators should require strong passwords, implement regular password changes, and mandate two-factor authentication for accounts with sensitive access. Single sign-on (SSO) integration with your organization's identity provider simplifies this and improves security.

Audit logs in Settings track who made changes to configurations, when integrations were added or removed, and what user actions occurred on the platform. Regularly review these logs to detect unauthorized access attempts or suspicious activity, particularly after staff changes or security incidents.

Best Practices for Managing Settings and Integrations

Document your integration setup clearly, including which systems are connected, what data flows between them, sync frequency, and any custom field mappings. This documentation helps new administrators understand your configuration and troubleshoot problems faster.

Review your integration and profile settings quarterly. As your business grows or processes change, integrations that made sense previously may no longer be optimal. Removing unused integrations reduces security surface area and complexity.

Train your team on profile customization so users fully benefit from personalization features. Many users are unaware they can customize notifications or dashboards and use default settings that don't match their workflow, reducing the value they get from GoliathData.

Establish role-based access control policies before adding team members. Define what each role can see and do, then assign roles consistently. Document these policies so that new team members and future administrators understand the reasoning behind permission structures.

Frequently Asked Questions

Can I test an integration before enabling it for the entire team?

Yes, most integrations in GoliathData support a testing mode or can be enabled for a subset of users first. When setting up an integration, create a test account with sample data and verify sync behavior. Once confident the integration works as intended, expand it to your production environment and all relevant users. Check GoliathData's documentation or contact support for specific testing procedures for each integration type.

What happens if I revoke access to an integration?

When you disable or revoke an integration, GoliathData stops syncing new data from or to that external system. Historical data that was already synced typically remains in GoliathData (unless you explicitly delete it), but updates will no longer flow. For bidirectional integrations, changes made in one system will not appear in the other. If you re-enable the integration later, GoliathData will resume syncing, though you may need to reconcile any changes that occurred while the integration was disabled.

Can multiple users share the same profile or login account?

No, each user should have their own profile and login account. Sharing accounts prevents proper audit trails, makes it impossible to assign accountability for data changes, and violates security best practices. If multiple users need access to the same properties or clients, grant them appropriate role-based permissions instead. This maintains security while allowing collaboration.

How do I ensure my data is not duplicated across GoliathData and integrated systems?

Configure your integrations to be the authoritative source for specific data types. For example, if your MLS integration is authoritative for listing data, do not allow manual property entry in GoliathData for listings (instead, they sync from the MLS). For client data, decide whether your CRM or GoliathData is the source of truth, then configure bidirectional sync to update the other system. Document these designations so your team knows where to make updates and understands the intended data flow.

Sources

• U.S. Census Bureau, QuickFacts, housing, ownership, and local market context.

• U.S. Department of Housing and Urban Development, official guidance on buying, financing, and distressed property.

• GoliathData real-estate records, distressed-property and market data compiled from public records.