Set up your company with an AI app
Once Pointmap is connected to your AI app, you can ask it to set up your company: “Make a Hold-down card type with a Result field that has Pass, Fail and Redo.” The app does what you can do in Setup and People, and asks you first when a change is hard to take back.
What can an AI app set up?
Section titled “What can an AI app set up?”- Fields: make, rename, describe and change a field’s settings, duplicate it, set its choices (and their colors), change its type, archive it and bring it back.
- Card types: make one, lay out its whole card in one change, change its name, description, color, icon and Instructions for AI apps, add and remove its fields, reorder them, set a field’s Required, Hidden and On the plan options, archive and restore it.
- Templates: make, rename, change the values of, copy and delete a template, add its photos and PDFs, save a point’s card as a template, and update a template from a point.
- People and access: invite someone by email, cancel an invite, change a role to admin, member or guest, suspend and reinstate a person, sign out one of their devices, make and change groups, and add or remove access to projects, folders, layers, card types, comments and fields.
Your app can also read what each setting does, so it picks the right one.
What stays in the app: join codes, making someone an owner, and removing a member. Starters aren’t available to an AI app, so ask for a card type and its fields instead. For the buttons to press yourself, see Make and change a card type and Create a field.
Who can?
Section titled “Who can?”Only owners and admins can set up fields, card types, people and access. A member or guest who asks is told so, and nothing changes. Templates are the one exception: anyone who can write cards of a card type can make, change, copy and delete its templates, and save a point’s card as one. Adding photos and PDFs to a template, and updating a template from a point, are for owners and admins only.
Your app acts as you, so a change shows in History as you, through your app.
What does it ask before doing?
Section titled “What does it ask before doing?”Making, renaming and changing settings happen at once. These always stop for your yes first:
- Archiving a field or a card type.
- Merging choices.
- Changing a field between Select and Tags.
- Taking a field off a card type while cards of that type hold values for it. The values stay on the cards.
- Every change to people and access, including invites.
One change is refused rather than asked: turning Multi-select off while cards hold more than one pick. The app names the cards, and you have each keep one pick, in Pointmap or through your app, before it can turn it off.
The app shows what would change. Say yes in the chat to make it, or say no and nothing changes. A change of more than 10 existing things asks too.
A request with several steps is one change: if any step can’t be done, none of them is made, and the app is told which step and why.
Can I undo it?
Section titled “Can I undo it?”Ask your app to undo it. It takes back the newest change it made for you: fields, card types, templates, saved filters and reports.
Two limits:
- People and access changes are never undone by an AI app. Invites, roles, suspensions, groups and access lines
stay until you change them back, by asking your app to do it with
pointmap_setup, or in Pointmap. - An undo is refused when someone else has changed the same thing since, or built on it: for example, when a person placed a point of the card type your app made. The app says who, and nothing changes.
Instructions for AI apps
Section titled “Instructions for AI apps”A card type has an Instructions for AI apps box in its settings, under its description (see Make and change a card type). Your app reads them, and each field’s description, before it places points of that type or fills in their cards.
Write what you’d tell a new hire: “Count one point per hold-down, at its center. Name points by grid line.” Ask your app to write them for you, too.
Advice, not a rule Pointmap enforces:
- Give every field a description. Apps read it to know what to put in.
- Keep the instructions short, about how to count, name and fill in. Put what a point is for in the description.
- Check an app’s first few points before you let it place hundreds.