Your sales director asks for access to GripIQ. They want to see which competitor shows up in the AI answers before sending a quote. You are happy to give them that access. You just don't want to run the risk that they, or a colleague, accidentally delete all the project's Prompts. That is what roles and permissions in GripIQ are for. The feature is little used, because it is rather tucked away: on a single tab under Settings.
Roles and permissions: what a role determines
Every team member sees every page of a project. The role determines what someone may change, spend or export. There are three roles.
- Team Admin can do everything in the project, and also manages the team, the connections with your own accounts and the Brands, websites and social media channels the project tracks.
- Team Member can do almost everything, but does not manage the team, does not set up connections and does not change the tracked Brands.
- Contributor is a limited role, meant for people who mainly look on and occasionally contribute.
Anyone you invite starts as a Team Member. Nobody gets the Contributor role automatically: a Team Admin assigns it deliberately. A role with no write access at all doesn't exist. So Contributor is the strictest option you have.
What a Contributor can and cannot do
A Contributor can still:
- add, edit and delete Prompts, one at a time;
- add and delete Keywords;
- link existing tags to Prompts and Keywords;
- mark an Insight as Useful or Not useful;
- use the chat assistant.
What a Contributor cannot do:
- bulk delete Prompts or Keywords;
- create or manage tags;
- generate AI suggestions;
- export data;
- change the status of an Insight (Apply, Schedule, Postpone, Reject);
- start tracking a discovered Brand as a competitor.
So a Contributor is not a read-only role: a colleague with this role can still edit a Prompt, one row at a time. What they cannot do are the actions with big consequences. Think of anything that affects the whole project in one click, anything that draws on your subscription (such as generating AI suggestions) and anything that counts as the shared status for the whole team, such as the status of an Insight. For sales and management, that is usually the right boundary.
Want someone to be unable to change anything at all? That role doesn't exist for customers. An agreement within your team won't solve that either, because the software does not enforce such an agreement.
Where you manage the roles
A Team Admin finds the Team members tab under Settings. There they can:
- invite colleagues by email, up to a maximum per invitation;
- change a team member's role;
- remove a team member from the project. That person's account and other projects remain unchanged.
How many people you can invite depends on your subscription. You can't change your own role or membership, so a project is never left without an admin.
One feature may surprise you: a role applies to every project someone is a member of, not only to the project you are working in at that moment. The app also says so next to the role selection. If a colleague is a member of two projects, they have the same role in both. If they are also in a project you are not a member of, you can't change their role.
An example: the sales director
Say you want the sales director and a business developer to look on. You open Settings, Team members tab, and invite them both by email. They start as Team Members.
If you want to limit what they can do, you change their role to Contributor. From then on, bulk actions, tag management, generating AI suggestions, exporting and changing the status of an Insight disappear. The sales director still sees Prompts, Keywords and Insights, and can still mark an Insight as Useful or Not useful. That way, sales signals which recommendations work in practice, without the status of an Insight changing for the whole team.
While you are at it, check who is Team Admin today. That role doesn't need to sit with everyone who was ever invited.
Why this makes a difference for sales
In essence, the roles solve a trust problem. As long as every invitation came with almost full rights, you only invited people you dared to trust with the whole project. Now you can widen the circle.
And for sales, that is no detail. Sales teams are closer to the buyer than marketing. They hear which questions buyers ask and which suppliers they mention. If that team is in GripIQ itself, it can check which Prompts match what it hears in practice. What happens before a lead ever calls you is explained in Lead generation starts before the first contact. How to write Prompts from the buyer's perspective is covered in How to write prompts the way a buyer looks for a supplier.
What you can do now
- Open the Team members tab and check who has which role.
- Invite the colleagues who currently look on via forwarded emails or a shared screen, and give them the role that fits their task.
- Agree that only a Team Admin assigns the Contributor role, and record for whom.
Open GripIQ and go to Settings, Team members tab.