Team seats and access grants: invite, share quotas, view/edit/download/delete

What the Team plan adds

Team (USD 89 / month) unlocks the same full HENFOIL product as Student and Professional, with the highest usage budgets, plus collaboration:

• Up to 10 seats invited by the Team owner
• Each member signs in with their own HENDOI account
• Monthly usage meters (polars, optimize, HEN-AI, PDFs, compute credits, etc.) are shared across the team
• Owner always sees members’ airfoils, projects and analysis
• Owner can grant another member view / edit / download / delete on a teammate’s work

Peer visibility is not automatic for every member. Until a grant exists, members do not freely browse each other’s private work (owner excepted).

---

Invite a seat

Where. Account → Team (on hendoi.com / your userid Team page). What to fill. Colleague email. Purpose. Send an invite so they join with their own login. Result. Pending invite → accept flow → active member consuming a seat. Remove when someone leaves so the seat frees.

---

Shared quotas — what to watch

Why it matters. One heavy optimize campaign burns the shared pool for everyone. Coordinate before large batch jobs.

---

Access grants (ACL)

Who sets them. Team admin / owner. What you choose. Target person’s work + grantee member + permissions:

Purpose. Controlled collaboration without making every seat a full admin. Result. Grantee can act within granted rights. Owner retains oversight of all members’ work. Email notifies when access is granted or revoked.

---

What members should expect

• Own login and own default private workspace
• Shared monthly limits with the team
• Visibility into a colleague’s artefacts only when granted (or if you are the owner)
• Email when your access changes

---

Admin checklist

1. Invite only people who should burn shared quota
2. Remove leavers promptly
3. Grant least privilege (view before edit/delete)
4. Confirm email notices after grant/revoke
5. Align the team on Re/mission conventions so shared polars stay comparable

Honesty reminder

Team features organise people and quotas. They do not change physics honesty — geometry gates and method IDs still apply to every polar the team runs.

In simple words: what this page is for

How Team plan seats work — own logins, shared monthly meters, admin visibility, ACL grants and email notices when access changes.

This lesson exists because section decisions fail when geometry, method labels and selection reasons are scattered. Team seats and access grants: invite, share quotas, view/edit/download/delete helps you keep a clean trail from shape to polar to choice.

Why the topic matters

Engineers lose time when a title sounds clear but the page only sketches the idea. This article expands Team seats and access grants: invite, share quotas, view/edit/download/delete so you can answer three questions without jargon: what is the idea, when do you use it, and how do you check it in a HENDOI product.

Read the sections above for the core definitions. Use the steps below to move from reading into a real project trail you can share with a teammate.

How to apply this in HENDOI

In practice: create a HENDOI account or log in, open HENFOIL, bring a section in (create, import DAT, or digitize), pass the geometry gate, climb the analysis ladder only as far as the decision needs, then compare and archive. Every calculated number should keep its method label.

When the section choice is ready for the aircraft, continue in HENSYNTH for mission, compliance and trades. Same account. Same plans.

What this page will not claim: a teaching polar or geometry note is not a flight-Re certificate. HENFOIL labels methods so you know what you bought. Tunnel data and professional judgement still sit outside any single software run.

Checklist before you leave this page

• Can you state the idea of Team seats and access grants: invite, share quotas, view/edit/download/delete in one sentence?
• Do you know which product owns the next action — HENFOIL or HENSYNTH?
• Will every number you keep carry a method label or a stored-run source?
• If you are new here, have you opened Register or Login?

Related reading on this site

• Airfoil selection with a documented why-#1
• The HENFOIL analysis ladder: when to escalate
• Create airfoil fields: NACA, analytic and CST — what each digit means
• Digitize field-by-field: every control, why fill it, what you get
• All HENDOI blog articles
• HENFOIL product page
• HENSYNTH product page
• Pricing — Student, Professional & Team
• FAQ
• Login · Register now