Most spaces include a Person object type. This guide shows how to grow that from a contact sheet into a network: people linked to companies, places, meetings, projects, books, and travel ideas—so context surfaces when you need it (prep for a call, planning a trip, “who do we know at…?”).

It assumes you are comfortable with object types, properties, and backlinks. For meeting-specific workflows, see Meeting notes; for saved lists on dashboards, see Queries in practice.

Start from the Person template

Add the Person template (or equivalent) so every person shares the same structure: title, tags, contact fields, image, category (for example personal / professional / family), and a body for notes—gift ideas, facts you want to remember, or anything else you prefer to keep on the object instead of only in prose.

Open Object settings for Person (menu on the type or on an instance). Changes there apply to every person object, past and future: you are editing the type, not a single page.

Extend Person with useful properties

Add properties from the type panel or via New property in settings. Examples that work across personal and work contexts:

• Date & time — Last seen and Last reached out (or similar) so relationship maintenance is visible at a glance.
• Text — Memory jog for small facts you do not want to lose; Job title when work context matters.

You do not have to fill everything when you create someone—capture the person first, then enrich during a weekly or monthly review. Table view on the Person type is useful for that bird’s-eye pass over columns.

Link people to organizations (“works at”)

To answer “who do I know at this company?” and to let company pages list contacts:

1. Add an Organization type (template or custom).
2. On Person, add an object select property named something like Works at. In the property settings, set the link to Organization and choose single or multiple organizations per person.

When you pick an organization on a person, the organization’s backlinks show everyone linked through that property—unless you use two-way linked properties, in which case the reciprocal property on the organization stays in sync with the person.

Link people to locations

1. Create a Location object type (icon and properties as you like).
2. On Person, add an object select property linked to Location for where they live or spend time (single location or multiple places).

Again, you might want to use two-way linked properties, so that the locations and people sync to the property automatically. Over time you can open a city and see who lives there from that one person property.

Countries and AI-assisted filling (optional)

To group locations under countries without typing the same country name everywhere:

1. Create a simple Country object type.
2. On Location, add an object select property Country, linked to the Country type.
3. If you use AI auto-fill on that property, Capacities can suggest a country from objects you already have—it will not invent a long list of entities you never created.

On the Location type’s table view, you can revisit rows later and use Fill when you are ready. AI-powered features require a Pro or Believer plan and AI enabled; without that, pick the country manually from the object select dropdown.

Meetings and projects

Add Meeting and Project types (templates are fine). Two patterns matter for people:

Object select vs text for “who was there?”

The Meeting template may ship with a text field for attendees. That is flexible: you can type names, paste text, or insert @ mentions and links to people. This is especially useful when someone appears once and you do not want a full Person object.

If you prefer a strict roster and dropdown creation, replace or supplement with an object select (multiple people) linked to Person. You can pair it with two-way linked properties so each person’s page shows the reciprocal “meetings they attended” field without relying only on backlinks.

Editing properties on the Meeting type affects all meetings; deleting a property removes it everywhere, so confirm when the app warns you.

Link meetings to projects

Add an object select (or text, if you want freeform) on Meeting pointing at Project.

Recommendations: books and places

Books

You can add a Recommended by property to the Book template. You can keep plain text or link to a Person so conversations (“I finally read what you suggested”) stay grounded in your network.

Places to eat, stay, or visit

You can split restaurants, hotels, and attractions into separate types, or use one Place type with collections or a category dimension:

• Add a Recommended by text property (names or @ links).
• Add an object select for Location (or city) so each place ties to your location objects.
• Use a label property (single or multi-select) for category (restaurant, hotel, attraction), with a fixed set of options so the dropdown stays focused. If you prefer categories drawn from your tag list, use an object select linked to Tag and still use a fixed set so the field does not list every tag in your space.

Queries vs collections (Pro)

On the Place type, New query with a filter such as Category includes hotel gives a list that updates automatically when new matching places exist. Choose table, wall, or gallery depending on whether you want columns, cards, or images. Pin to dashboard nests the query under the type (and on the object-type dashboard). Duplicate the query and change the filter (for example to restaurant) instead of maintaining parallel manual collections.

Collections stay manual; queries stay rule-based. Use both if you like a curated “best of” list alongside an exhaustive auto list.

Where to go next

• Content types — built-in and custom types
• Properties — object select (single or multiple), labels, dates, and link targets
• Object properties — two-way linked properties, fixed sets, and customization
• Backlinks — embed layouts and relationship labels from property names
• Meeting notes — templates, calendar, tasks
• Queries in practice — dashboards and embeds
• Daily notes — capture and review before objects exist
• Bulk actions — turn blocks into objects
• AI assistant — plan features and opt-in behaviour