Warframe clan roles and permissions

Separate the three systems

Your in-game clan rank, Discord server roles, and Warframe Clan Finder management access are separate systems. Authority in one does not automatically grant permission in the others. A clear recruitment team knows who can invite a player, who can moderate a conversation, and who can update the public listing.

Give people the access their task needs

Official Warframe guidance describes permissions for invitations, research, building, moderation, and other responsibilities. Review the current in-game options before changing a rank. Use the smallest set of permissions that supports a person’s job, and explain which decisions require discussion with other leaders.

A helpful recruiter does not necessarily need responsibility for every building project or account. Start with a clear role, review how it works, and expand access only when there is a reason.

Make handovers practical

Maintain a private responsibility list with a primary and backup contact for recruitment, member concerns, Dojo questions, and public information. Store process notes where the relevant team can access them without sharing personal passwords. When a person leaves leadership, review all three systems rather than assuming one role change completes the handover.

Set expectations for members

Publish a short explanation of whom to contact and what an escalation looks like. Avoid treating a rank name as a complete description of someone’s powers. If a member cannot access a feature, check the actual permission and current rules before describing it as a technical fault.

On this directory, claims are reviewed through the support process and account controls appear under Manage listings. Read the listing rules and the maintenance guide when changing representatives.