Frequently Asked Questions

Craftly Workspace is the central system Craftly uses to coordinate people, work, communication, resources, and day-to-day operations.

Start the onboarding process through the official Craftly joining system and complete the required questions and steps. After onboarding is completed, you will receive your Private Key, Workspace and Craftly Robot acess.

Your Private Key is a sensitive part of your Craftly identity and is required to log in to Craftly Workspace. Keep it secure and never share it with anyone.

If you are still logged in to Workspace, you can request a new key from your Profile. If you are logged out, recovery may require the account recovery or verification process.

No. Your Private Key should remain private. Never send it to another member, post it publicly, or store it somewhere insecure.

After completing onboarding, you wait for your organizational position to be assigned. Once your position is active, you can begin your responsibilities within Craftly.

The Command Chain is Craftly's hierarchical system for passing official commands, instructions, and tasks through the organization. Chairman → CEO → C-Suite → Senior → Junior → Executive

Official tasks can be distributed through the Notice Board or through the Command Chain, depending on the nature of the work.

The Notice Board is the official place for organizational announcements, important messages, updates, instructions, and other information that needs to be communicated to members.

Use the Task Submission option associated with the task. You can submit up to 5 files, including images, PDF, text, JSON, or CSV.

If you are unable to complete an assigned task, contact your Unit Leader and explain the problem or blocker instead of leaving the task unresolved.

Projects are practical work assignments, primarily used within Operations, that help members demonstrate their ability to understand requirements, solve problems, use technical tools, and deliver real results.

Go to Work > Department > Projects and open the relevant project. Download the project package and read the included AGENT.md file before starting.

AGENT.md contains the project's specific instructions, requirements, rules, technical expectations, and other information you need to understand before working on the project.

A Support Request allows members to ask for help or report an issue through a structured system instead of relying only on informal communication.

You can submit requests for: Unit Commander Technical Issue Legal or Safety Attendance Correction Ethics Report Suggestions Private Key Recovery

If your Unit Commander is inactive, does not provide clear instructions, or does not properly explain what to do, how to do it, where to do it, or why the work is required, you can report the issue through the appropriate Support Request.

Create a Technical Issue Support Request and provide enough information about the problem so the responsible team can understand and investigate it.

Yes. Use the Suggestions Support Request category to share ideas, improvements, or feedback that could make Craftly better.

Stay ready for your position to be assigned. Once active, understand your responsibilities, stay involved, complete your work sincerely, communicate clearly, and continue improving.

First, download the project package and read the AGENT.md file carefully. It contains the project's objectives, instructions, requirements, and technical guidelines. If you still don't understand the task after reading the instructions, do not guess or make random changes. Contact your Unit Leader or use a relevant Support Request to ask for clarification.

After completing and testing the project, follow the project's provided Git workflow to push your code to the designated Craftly repository/server. Make sure you have followed the AGENT.md instructions and that your final work is properly committed and pushed. If the project also requires a formal Task Submission, submit the completed work there as instructed.

Your organizational position and responsibilities will be available through Craftly Workspace once your position has been assigned. Make sure you understand your role before taking responsibility for work.

Start with your Unit Leader. If your Unit Leader is unavailable or is not providing enough guidance, you can submit a Unit Commander Support Request.

No. Complete your onboarding first and wait for your organizational position to be assigned. Once your position becomes active, follow the responsibilities associated with it.

First, try to understand the issue and check the available project instructions and resources. If you are still blocked, contact your Unit Leader and explain exactly what is preventing you from continuing.

Do not silently leave the task incomplete. Inform your Unit Leader as early as possible, explain the reason, and communicate what support or additional time you may need.

Not unless the project instructions allow it. Always read the project's AGENT.md and follow its requirements before making significant changes.

Follow this basic workflow: Download → Extract → Read AGENT.md → Understand Requirements → Set Up Environment → Work → Test → Commit → Push → Submit

Check the relevant Department Resources in Craftly Workspace first. Project specific resources may also be included inside the project's downloaded package.

Your submission can be reviewed according to the project's requirements and organizational workflow. The result of your work may contribute to evaluating your ability to handle future responsibilities.

Only when the responsible leader or project instructions explicitly allow it. If you cannot finish the work, communicate the blocker instead of submitting something incomplete as if it were finished.

If the submission can still be corrected, follow the project's submission instructions or contact your Unit Leader. Avoid repeatedly submitting incorrect versions without first understanding what needs to be fixed.

Do not make assumptions about an official task. Ask your Unit Leader for clarification and explain exactly which part of the instructions is unclear or conflicting.

Projects are also an opportunity to learn. Start by reviewing the provided instructions, resources, and project documentation. If you remain blocked, ask your Unit Leader for guidance or request appropriate support.

Keep communication clear, respectful, relevant, and timely. When discussing work, provide enough context so the person receiving your message understands the situation without unnecessary back-and-forth.

Use the appropriate Support Request category, such as Legal or Safety or Ethics Report, depending on the situation. Avoid sharing sensitive information in public organizational channels.

If you know that you will be unavailable and it may affect your responsibilities, communicate with the appropriate leader beforehand whenever possible.

Focus on consistent execution, technical growth, reliability, communication, and understanding your responsibilities. Practical project performance and your contribution to the organization can help demonstrate that you are ready for greater responsibility.

Be transparent about it. Inform the appropriate person, explain what happened, and work toward correcting it. Hiding a mistake can create a larger problem; communicating it early gives the team a chance to resolve it.

No. Craftly Workspace is the current operational system for coordinating people, work, communication, and organizational processes. Craftly Robot is Craftly's active agentic-AI research and development direction.

If you cannot find the answer in the documentation, use the appropriate Support Request or contact the responsible person through the organization's communication structure.

Department placement can change when Craftly's needs or a member's skills, responsibilities, and performance change. Any change should follow the appropriate organizational process.

Yes. Members may collaborate across departments when a project, task, or organizational requirement requires it. Your primary department still determines your main responsibilities and resources.

Yes. Roles are not necessarily permanent. Your responsibilities may change based on demonstrated reliability, quality of work, technical ability, leadership, communication, and organizational needs.

Your position is determined by Craftly's Board Members and top level leadership, including the C-Suite, based on the organization's current needs and your demonstrated contribution, reliability, skills, and performance.

You can communicate your interests and goals to your manager or the appropriate leadership. Role changes depend on organizational needs and whether you are ready to take on the responsibilities of the requested role.

A task may be reassigned when priorities, responsibilities, or organizational requirements change. Follow the updated assignment and ask your manager if anything about the change is unclear.

If you have a genuine blocker or cannot reasonably complete a task on time, communicate with your Unit Leader as early as possible and explain the situation. Do not wait until after the deadline without communicating.

Review the feedback, understand what needs to be corrected, make the required changes, and resubmit the work according to the task instructions.

This depends on the task and the Workspace workflow. If you need to change a submission, follow the available correction process or contact the responsible leader.

The Task Submission system currently supports up to 5 files per submission. Combine or organize your supporting material when necessary, while following the project's or task's submission requirements.

Work is generally reviewed through the appropriate reporting and management structure. The responsible reviewer can depend on the task, department, and member's position.

This depends on the project's instructions. Always read the project's AGENT.md file and follow its specific rules about AI tools, external services, and development practices.

Only when the project instructions allow it. If a project provides a specific environment, MCP configuration, repository, or workflow, follow those requirements rather than replacing them without approval.

Project files should be treated as internal organizational resources unless explicitly marked otherwise. Do not publish, redistribute, or share internal project materials without appropriate permission.

When a project provides a Git workflow, you should follow the required process, including committing and pushing your completed work to the designated repository before making the formal submission.

First, check the project's AGENT.md, setup instructions, dependencies, and provided resources. If the problem continues, contact your Unit Leader or submit a Technical Issue Support Request with the relevant error details.

Use the appropriate reporting or Support Request channel and provide enough information for the issue to be investigated. Include steps to reproduce the problem when possible.

First check your Workspace notifications and relevant communication channels. If the issue appears to be technical or prevents you from receiving required information, submit a Technical Issue Support Request.

Profile information can be updated through the available Workspace profile settings. Some information may require additional verification or administrative approval.

Access to personal and organizational information should depend on the member's role, permissions, and legitimate organizational need. Sensitive information should not be exposed more broadly than necessary.

Attendance can contribute to organizational participation and performance signals. Consistent attendance helps demonstrate that a member is actively participating in their responsibilities.

Yes. Performance signals are dynamic and can change as your activity, verified work, attendance, participation, and other contribution signals change. Other members' increased contribution can also affect your relative department ranking.

No. Department rankings are live and can change over time. The ranking reflects current contribution rather than a permanent position or title.

No. Completing onboarding only establishes your membership process. Compensation is intended for verified members who have an active role and are contributing to real Craftly work under the applicable compensation structure.

Craftly is currently operating as a non-profit organization, so regular salary payments are not yet active across the organization. A structured compensation system is planned as Craftly secures funding and establishes the required infrastructure.

Once the compensation system is available, eligible verified members will be able to manage payment information through their Craftly Workspace profile. Supported options may include bank accounts, bKash, and other supported payment gateways.

Members can communicate their intention to leave through the appropriate organizational process. Any responsibilities, active tasks, projects, or organizational access should be properly handed over before leaving.

Extended inactivity can affect your responsibilities, communication, performance signals, or organizational position. If you expect to be unavailable, communicate with your manager as early as possible.

If you believe a decision affecting your role, responsibilities, or access needs to be reviewed, raise the matter through the appropriate reporting or escalation path and provide clear reasons and evidence.

You should first communicate respectfully with your manager and try to understand the reasoning behind the decision. If the matter cannot be resolved, use the appropriate reporting or escalation process rather than bypassing the organizational structure.

Do not ignore the situation or proceed blindly. Ask for clarification when appropriate and use the relevant Legal or Safety or Ethics Report Support Request if the instruction involves a serious safety, legal, or ethical concern.

Direct communication with senior leadership is controlled to protect privacy and maintain clear organizational boundaries. If you need to reach someone above your access level, follow your reporting structure and ask your manager or Unit Leader to facilitate the communication.

Only when that contact is officially available to you. Do not obtain or use another member's private number without authorization. Follow the reporting structure when direct contact is not provided.

No. Craftly Robot is a real AI system with conversational capabilities, but it is being developed toward a broader agentic model that can discover relevant people, services, and agents and coordinate real-world tasks through agent-to-agent communication.

No. Craftly Robot is currently under active research and development. Its agentic capabilities are being built progressively, and consequential real-world actions are intended to remain subject to appropriate human review and confirmation.

This is one of the core directions of Craftly Robot. Agent-to-agent communication and negotiation are being actively developed so that agents can discover, communicate, align requirements, and coordinate possible solutions.

Craftly Robot is being developed toward a broader ecosystem where specialized agents and capabilities can participate in the network. The exact tools and public development workflow depend on the current Robot release.

Not automatically. Agents can help discover participants, exchange information, and negotiate possible conditions, but consequential commitments should remain subject to appropriate human confirmation.

The agents can report that the requirements could not be aligned and return the available information to the user. The user can then modify the requirements, choose another option, or stop the process.

Robot may ask follow-up questions to clarify your goal, requirements, or constraints. The clearer your request, the more effectively the system can determine what should happen next.

Access should depend on the capabilities and permissions available to the Robot application. Robot should not be assumed to have unrestricted access to every device resource.

No. Agent communication should operate within defined identity, permission, and privacy boundaries. Only information relevant and authorized for the task should be shared where appropriate.

The Robot should treat information received from another agent as input to be evaluated rather than automatically assuming it is correct. Important decisions should remain reviewable, especially when they may have real-world consequences.

Check the Craftly Release Notes for new features, improvements, fixes, and product changes across Craftly Workspace and Craftly Robot.

Use the official Craftly documentation from the main website. Product-specific documentation is organized separately for Craftly Workspace and Craftly Robot.

Check the relevant product documentation first. If your question is still unresolved, use the appropriate Support Request category or contact the responsible person through your reporting structure.