Shared research and monitors
Use Teams or Teams Plus for a pentest team, an internal security team or an API integration. All members draw from one organization credit pool. Client folders are optional.
1. Research together
Open Teams → Search to use the shared research space. The context bar shows the organization paying for the operation. Search, Pivot and tools retain this context as you navigate. Organization membership does not combine personal and shared credit balances.
2. Follow changes with monitors
Open Teams → Monitors. Use the common space, or select an optional client folder to group its monitors and spending. Choose the dataset and query:
- Hosts: observed services and their attributes.
- DNS: observed names and values.
- Certificates: covered names and certificate changes.
- WHOIS: registration observations for the exact domain.
Review the query, page limit, credit cap and frequency. Validate the query and estimate before saving. Scheduled collection requires explicit activation. The first usable collection establishes the baseline. See Monitoring for limits and change review.
If you use a folder's declared domains to prepare a query, including subdomains matches the exact name and descendants for Hosts, DNS and Certificates. WHOIS uses the exact domain; it does not infer a separate registration for each hostname.
3. Connect your tools
Use API integrations for organization service keys with explicit permissions, research contexts and credit ceilings. Automation can use the shared space without a client folder. The API returns asynchronous jobs; poll their results instead of resubmitting a search. Start with the Service API or MCP and n8n examples.
What observations establish
Research monitors read Profundis datasets. They are not active scans or continuous availability checks. Observations may be partial or old, and a newly indexed record can describe an earlier observation. Missing data does not prove disappearance. Use the source and observation date when deciding whether to investigate.
For active endpoint checks and automatic asset monitoring, use Exposition. Historical cases and reports remain available in the previous workspace tools; creating them is optional.