WinGrid
A website key can write leads only for its own entity. The secret is stored as a hash. The same phone updates that person instead of creating another lead.
Product
Organizations, entities, keys, fields, and stages are separate. Nothing on this page is sample pipeline data.
Inside an entity, a phone belongs to one lead. Sending it again updates the person. The stage does not move.
The access key selects the entity. The secret is shown once. Revoking the key stops new pushes.
Each entity has its own stages. A later stage moves the lead forward. The next entity can use a different path.
A super admin grants Dashboard, Leads, Lead Management, and Settings. People stays with the super admin.
How it works
The website cannot choose a different entity. The key does.
Step 1
Every lead, field, stage, and API key belongs to one entity inside one organization.
Step 2
The website gets an access key and a secret. The secret is shown once. WinGrid keeps only a hash.
Step 3
A new phone starts on that entity’s first stage. The same phone updates the lead and does not move the stage.
Step 4
Stages belong to the entity. A later stage can move the lead forward. Another entity can use a different path.
FAQ
Yes. Leads, fields, stages, and API keys belong to one organization, and a key can write only for its own entity.
Yes. You set the stages for each entity. The key stays stable. Changing a label updates the leads already on that stage. Moving leads onto another stage is an explicit map.
The existing lead is updated. Name, email, page, and the fields you send can change. The stage stays where it is.
Only a hash. The secret itself is shown when the key is created. Revoking the key stops new pushes. Leads already stored stay.
Sign in to the workspace for your organization.