<aside> πŸ’‘ Provide a detailed overview of the functionalities.

</aside>

Stackles is built to boost your teams productivity and make it simple and fast for you to easily manage access to your files, links, and tools.

Any individual and organisation can use Stackles to improve onboarding, collaboration and navigation within teams, communities and groups. The tool at it’s core enables team to achieve these three things:

The Stack

An organisation/admin can stack tools, files and links in one place, making it easy for quick access to this assets when they are needed. This is seen in our MVP features of Collections, Boxes and Teams.

Collections

These are different stacks of all the links within an organisation. Here the admin can easily create a new collection within an organisation and keep adding important links to the collection. The user can be able to share a particular collection to individual team members or invite a whole team ( β€” These teams have special permission requirements or not β€” ).

In later features, there will be added features that enables the user to import links from their bookmarks and also export links to their bookmark.

Boxes

These are different stacks of all the files uploaded within an organisation. Here the admin can easily create a new box within an organisation and manually upload files within a box and add recordings of video/audio files of sessions from events done in Discord. The user can be able to share a particular box to individual team members or invite a whole team ( β€” These teams have special permission requirements or not β€” ).

In later features, there will be added features that enables the user to import files from third-party file storage integrations and also export files to their third-party file storage tools.

Teams

<aside> πŸ’‘ The purpose of teams in the organisation is for categorising the different workstreams within an organisation β€” Workstreams refer to distinct components or streams of work within a larger project or initiative. They represent specific areas or tasks that need to be addressed and accomplished to achieve the overall project objectives. Workstreams are often used to break down complex projects into manageable and focused sections, allowing teams to organise their efforts and track progress more effectively.

Each workstream typically focuses on a particular aspect of the project and may involve different teams or individuals with specialised skills and responsibilities. Workstreams can run concurrently or sequentially, depending on the project's requirements and dependencies. They help provide structure and clarity to the project, ensuring that different activities and deliverables are properly coordinated and aligned towards the common goal.

Workstreams often have their own goals, timelines, milestones, and resources assigned to them. They enable efficient collaboration, as teams can work independently on their respective workstreams while maintaining overall project visibility and integration. By dividing the project into workstreams, it becomes easier to manage complexity, allocate resources, identify dependencies, and monitor progress.

Examples of workstreams in various projects could include design and development, marketing and communication, research and analysis, procurement and supply chain, testing and quality assurance, implementation and deployment, training and support, and so on. The specific workstreams depend on the nature of the project and the goals it aims to achieve.

</aside>

This is where the members of an organisation who are not admins lives. This can be created and managed from the teams page or the settings page for organisations. There can be custom access requirements settings set by the admin for teams and there can also be free access teams β€” these are teams created without any access requirements.

For teams with custom access requirements, the access requirements for teams collections, boxes and tools who are web3 based organisations and communities would be based on participation and engagements elements like Token, NFTs etc. Some of the options we can provide for admins to set to manage access are covered more extensively below. This design is with respect to the fact that these members would be signing up with their wallet address and under the hood we also provide a single sign-on system for organisations for all their tools.

Here are some common assets that can be stored in a blockchain wallet for DAO access management:

  1. Cryptocurrencies: Blockchain wallets typically support the storage of various cryptocurrencies, such as Bitcoin (BTC), Ethereum (ETH), or other altcoins. These cryptocurrencies can be used for participation in DAOs, including acquiring or staking governance tokens or participating in token-based voting systems.
  2. Governance Tokens: DAO-specific governance tokens are often stored in blockchain wallets. These tokens represent ownership or voting rights within the DAO and can be used to participate in decision-making processes, vote on proposals, or delegate voting power to trusted parties.
  3. Non-Fungible Tokens (NFTs): NFTs are unique digital assets that can represent ownership or access to specific items, such as digital art, virtual real estate, or in-game assets. NFTs stored in a blockchain wallet can grant access to exclusive features or privileges within a DAO community.
  4. Reputation Tokens: Some DAOs issue reputation tokens that represent a member's reputation or influence within the community. These tokens can be earned through contributions, expertise, or community engagement. Storing reputation tokens in a wallet allows members to showcase their reputation score and potentially gain additional privileges or voting power.