Community member
Personal profile and membership status, news and events, messages, documents and dues, voting, elections, comments, requests for support and privacy settings, within the enabled modules.
A separate mobile product designed first for community members. Founders, the leader and administrators will receive their own workspaces and capabilities according to their responsibilities.
After signing in, each person will see only the capabilities assigned to their role in the company, club or organisation. A member will have a simple personal space for community interaction. Founders will see the strategic picture, the leader will see current operations and matters requiring a decision, and administrators will have tools to maintain data, access and workflows. A person who combines roles will be able to switch between their approved workspaces.
The exact modules will be configured around the organisation’s rules and processes. The core model separates four workspaces.
Personal profile and membership status, news and events, messages, documents and dues, voting, elections, comments, requests for support and privacy settings, within the enabled modules.
A strategic view of community development, key indicators, important initiatives, aggregated trends, critical escalations and matters requiring a founder decision.
The daily operational picture: community activity, team tasks, unresolved requests, contributions, events, early signals and follow-up on agreed decisions.
Member records, invitations and onboarding, roles and access, news and events, documents, payments, requests, module configuration and data preparation for reports.
Define member types, founder, leader and administrator responsibilities, important scenarios and the data each role needs.
Agree on functions, navigation, name, visual identity, languages, messages and interaction rules within the app.
Integrate agreed Cikavo products, the member directory, payments, communications and other systems required by the organisation.
Test every scenario and access level, run a pilot with representatives of each role, resolve confusing areas and prepare for launch.
Members will have clear mobile access to the community, their actions, documents, payments, decisions and available services.
Founders, the leader and administrators will receive the right overview and action tools without unnecessary access to personal information.
The organisation will be able to add modules and products gradually while keeping a familiar member experience and clear access rules.
The mobile app will bring everyday community interaction into one place. Each role will have a clear workspace for its tasks, while the organisation can communicate faster, carry out decisions and maintain connections with people as it grows.
Yes, we envisage one mobile product with different workspaces. After signing in, each user will see functions for their role, while a person with multiple roles can switch between their permitted workspaces.
Use a personal profile, view membership information, news, events, messages, dues and documents, participate in community decisions and request support. The exact set will depend on the modules enabled by the organisation.
That capability is part of the product design. An organisation will be able to define and combine roles, assign permissions and restrict access to sensitive functions and data.
It will be a separate product and can also become a mobile access point for selected modules, such as dues, communications, voting, requests and other services the organisation chooses to enable.