| Description |
Summary |
When you sign up on Rundl you get a free personal account, which you can use to participate in services. Participating is main thing to do on Rundl, but you can also belong to things, like a group for your work/business. |
Profiles |
This is your identity on Rundl. It's got a profile photo plus fields for name, bio, mobile, URL, location and professional title/role. Profiles are commonly shown in activity feeds to show who posted something. Profiles can be made private (restricted to other participants or group members). |
Multiple account emails |
Personal accounts may have multiple emails, typically separate personal and work email addresses. Adding extra emails ensures people get invitations to any address routed to a single Rundl account. There's no need to manage multiple logins. Notifications can be configured to send to any account email. |
Gravatar |
Account holders can configure in fine grained detail which types of notifications they receive. Especially for busy participants, getting the right notifications is crucial for using Rundl successfully. |
Notification settings |
Account holders can configure in fine grained detail which types of notifications they receive. Especially for busy participants, getting the right notifications is crucial for using Rundl successfully. |
Request settings |
Account holders can configure getting invitations to participate in rundls, or getting requests and approving each rundl they participate in. |
Summary |
Group accounts give your business a presence on Rundl. Bring your people together to work under your brand and get greater administrative control and security. |
Profile |
A group's profile includes a logo icon, cover image, plus fields for name, description, website and video URL. Groups are searchable in the network. Group profile details are shown in activity feeds when a user is participating in a group context. Business can promote their brand in transactions and be easily found on the network. |
Members |
Groups can have an unlimited number of members. Members are typically people who work in the business. |
Teams |
Teams connect group members. These members usually have common responsibilities and teams simplify how they manage their shared work. Adding a team as a rundl participant once reduces the overhead of adding each member one-by-one. With shared access members can cover each other for contingencies, such as leave or resignations, or divide work up into manageable chunks. |
Subscriptions |
A group owner can subscribe to different plans to unlock additional capabilities. On our standard plan a free trial period is available. |
Group owner |
The group owner is the person responsible for the account and its associated data. By default the person who creates the group is the owner, but ownership can be re-assigned later. |
Administrators |
Each group has a default Administrators team. Members of the Administrators team get elevated privileges, such as the ability to manage the group's profile, account, members, teams, requests and various settings. |
Private members and teams |
Group members and teams can be flagged as private. Private members and teams won't be found by third parties when they search for participants to invite to transactions. |
Request settings |
Groups can choose to get a request when they're invited to participate in a rundl or to skip requests and get added straight in. A setting can be used to determine the default team if it's not explicitly selected. |
Templates |
Templates are standard text or files that can be selected when posting in a transaction. Making standard content into templates helps participants save time and be consistent. Templates are searchable and can be filtered by service type. |
Summary |
Services are the blueprints for the different kinds of transactions delivered on Rundl. A service has name, description and category details to identify it and aid in discovery. It also has steps that detail the process involved. A service is owned by a group account and is managed by its trusted members. A published service can be ordered on Rundl. |
Service profile |
Service profiles are the face of a service and help make it discoverable to other people in the network. A service profile has a name, description, branding, metrics and video content. |
Process model |
Process collaboration is central to how services get delivered on Rundl. A service model is the process part of the service. It specifies the unique steps, roles, permissions and related settings that defines the type of service. Account holders can use a pre-configured Rundl platform services, or with an Enterprise plan, fully customise their own models. |
Platform services |
Rundl provides pre-configured services that hosts can clone into their account to make it simple to get started. |
Subscribers |
Service managers can invite other people or groups to subscribe to their service. Subscribers can be assigned the right to start and host rundls. Subscribers get access to the work board view to track their rundls, and can create related services for referrals. |
Managers |
A manager is the subscriber that has privileges required to setup and configure a service. They do administrative tasks like managing the service's profile, subscribers, design, settings and related services. With custom services, managers are also responsible for building the service model. |
Related service network |
Service providers can build a network of trusted services for referrals. Related services can include both an account owner's own services and services provided by referral partners. Service providers can create a related service, set a referral fee, and from then on offer the service to participants within their rundls. |
Working in context |
When a user ends up subscribed to a service with multiple contexts from the same group, their access must always be scoped to a single context. By switching contexts they can access the service with different privileges and views. Initially a default context is applied and this remains active until they switch. |
Status |
Services have an overall status: open or closed. Closed services are not shown in the main service view and can't be started or ordered. Services also have an operational status: active or paused. Paused services can be ordered, but new rundls can't be started. Pausing allows a manager to make a batch of changes to a service model without getting any new rundls started before they've finished. |
Category tags |
Tags can be applied to categorise a service. Some system features depend on services being categorised with tags. |
Branding and design |
Services can be decorated with common design attributes, like a background colour and header image. |
Custom invitation message |
Managers can override the default message that is shown when participants are invited in rundls. |
Order service instructions |
Managers can override the default order instructions that are shown to people when ordering their service. |
Summary |
Service models are the process template component of a service. The model encapsulates all of the configurations that get used to define the process in a rundl. |
Steps |
A step is something that gets done in a rundl. Service managers add a series of steps taken when delivering their service. For example, the steps in a basic "Build a House" service could be: 1. Lay foundation. 2. Erect walls. 3. Add roof. 4. Insert windows and doors. The steps give structure to the collaboration in a business transaction and ensure the process is transparent for participants. Each step has a name, description and rich content like YouTube videos, images and attached documents. |
Step workflows |
Steps may optionally have workflows. Step workflows provide the ability to track the status of steps in rundls via status updates. |
Private steps |
Private steps are hidden in service profiles. For example, service providers can publish a service but still hide certain steps that are used for internal purposes only. |
Roles |
Roles are labels for the different type of participants in your service. You add roles to your service model once, then assign them to participants in each of your rundls. Roles also allow you to control access to information in your rundls. |
Role barriers |
Role barriers is a configuration option for hosts that bars certain participants in a rundl from communicating with each other. When a participant posts a message, barriers override who can see the message, based on the participants' roles. |
Step permissions |
Step permissions can be configured for each role, allowing fine grained control over who can see and update the status of steps in rundls |
Step-filtered related services |
Tags that match the category tags on related service can be offered in this step. In rundls, any related services with matching tags will be available to participants for ordering from within the context of a step. |
Summary |
Rundl is a channel for acquiring new customers and transnational work. Rundl makes it possible for services providers to offer services through a network of referral partners and track job requests |
Approval queues |
Each orders is presented as job request that can be reviewed and started by approval. |
Referral fees |
Set referral fees for your referral partner arrangements and track the fees you're owned and acknowledge completion of the referral cycle. Partners can also see the referral fees they owe from job requests received on Rundl. |
Summary |
A rundl is a shared digital space that brings together people and information around a business transaction for communication, collaboration, visibility of process and application integration. A rundl can be started for any type of business transaction, such as cases, jobs, deals, applications or procedures. |
Rundl status |
Rundl status is the overall status of a transaction, represented by a label. Active rundls are in progress (all rundls become active when started). Completed rundls are done. Cancelled rundls are closed and will not be completed, possibly due to an exception in the process. The overall rundl status is also represented as a percentage, based on the ratio of completed and uncompleted steps. |
Participants |
Participants are the stakeholders in the business transaction that's getting delivered as a rundl. People, organisations or teams within organisations can participate in rundls be assigned roles. Usually one participant, the host, invites the other participants to take part. |
Hosts |
The host of a rundl is the lead service provider in the transaction and manages the delivery and operation of the process. The host moderates the collaboration and performs administrative tasks like managing participants, assigning roles, applying branding, updating the status etc. Only service subscribers assigned the "Can Host" permission can be selected to host a rundl for that service. |
Context |
As group members may belong to multiple teams, sometimes a member will get access to one rundl via multiple participants. This is an advanced scenario. When this happens the members access to the rundl access will be scoped to just one of these participation contexts. Initially a default context is applied, but the context can be switched. Depending on the the selected context different content and privileges may be available. |
Change and duplicate participants |
Participant groups can manage their own participation by changing or duplicating their access. Changing a participant context changes access from one context to another. For example, a member of Team X in Group A might change the participant to Team Y in Group A. Now only Team Y is a participant. Duplicating a participant grants access to an additional context in the group. For example, a member of Team X in Group A might extend access to Team Y in Group A. Now both Team X and Team Y are participants. |
Observers |
A host can optionally make a participant an observer. Observers can't post messages or comments. |
Steps |
A step is something that gets done in a rundl. Steps are an important part of Rundl's unique method of process collaboration. Once started, each rundl gets a copy of the steps from its respective service model. These rundl steps implement the step capabilities configured in the service model, such as videos, images, rich text for communications, and role permissions for access control. |
Step status |
Steps in a rundl can optionally have workflow. Transitions through various states (e.g. open, active, completed, cancelled) give participants visibility over how work on that step is tracking. With all steps presented together in a series, the overall status of a transaction can be visualised. When steps are completed, the actor can apply an effective completion date if they've completed the step at another time. Permissions control who can update a step's status. |
Step due dates |
Each step can be assigned a due date. The date features prominently to inform participants of critical dates in the overall process. For hosts looking at the work board, due dates drive program delivery - with colour transitions indicating relative proximity to deadlines. |
Messages |
Communication in rundls starts with messages. With messages it's easy to share information with other participants securely. Messages may include multiple attached documents or links. By default a message will be visible to all the other participants in a rundl. But its visibility can be limited to one or more individual participants or roles, in any combination. Authors can also update or delete messages after they've posted. Note that a host of a rundl acts as moderator -- he or she can remove messages authored by other participants, but can't update the content. |
Comments |
Participants can comment on messages to provide feedback or discuss the content. Comments inherit visibility from the parent message. |
Files |
Rundl files include both files attached to messages and any files uploaded directly to the rundl. Only hosts can upload files directly. Where attached, permission to see a file extends from the permissions on the message. When looking at a file, participants can download it, view file metadata, and conveniently link back from the file to any attached messages. Enterprise hosts can also activate file versioning for a full and compliant record of file updates. |
Visibility |
Visibility lets participants choose the precise audience when posting messages or files. The feature allows selecting a set of participants and/or roles for each post. In practice it means participants can have private discussions within their overall transaction community. When visibility is granted to a specific participant, the content is visible just to them. If granted to a role, it's visible to any participant assigned that role now and in the futre. |
Related services curation |
Hosts can curate the related services offered in each rundl by selecting the appropriate services in their service network. Curation produces a set of related services that are relevant, contextually, on a case-by-case basis. For example, hosts may curate services available in their customer's suburb or location. |
Offer related services in steps |
Service providers can offer related services in steps for a more intuitive order referral experience. Hosts will can trigger marketing emails by activating a step. Participants will receive the notification and click a link to view the step, see marketing information, and choose from a range of offers from other service providers on Rundl. |
Related rundls |
When participants order a related service, once the order is accepted it is delivered in parallel as a related rundl. Participants can see their network of related rundls. |
Rundls filters |
Rundls can be filtered according to a range of properties. This includes filtering by full text on rundl name and description (e.g. show me all my rundls where description includes "Prahran", by rundl status (e.g. show me all my "Completed" rundls), by service (e.g. show me all my "Real Estate Sale" rundls), by participant (e.g. show me all my rundls where "Jo Consumer" is participating), by step status (e.g. show me all my rundls where "Contract Exchanged" step is completed). |
Fields |
Store custom data within the context of a rundl transaction. Ideal for integrations, fields are defined on a service model and can be populated in any corresponding rundl. A field may have a custom type and schema, or use one of the default primitive types. |
Pins |
Hosts can pin messages from activity to bookmark a list of important posts for quick access. |
Summary |
People may access information and act in Rundl using different security contexts. Context is Rundl's solution to the data access controls required in multi-sided transaction. It's transparent to regular participants until they join a group and acquire an additional context. |
Accounts |
Most interactions on Rundl are scoped to an account. People act either under their personal account, or under one of their group accounts. |
Group contexts |
A group member's access to rundls and services may be scoped to a further, lower-level context. Group contexts cater for multi-dimensional access to data and capabilities according to typical scenarios arising with most organisational structures. Groups, teams and members are all distinct security contexts that can be granted access to information and privileges, allowing advanced access controls and contextual views of business transactions. |
Summary |
Requests is an approval queue that let's you control your connections on Rundl. Approve or deny requests to join groups and teams, participate in rundls, or subscribe to services. Configuration settings allow account holders to opt in automatically to some types of requests. |
Request status |
Track pending and completed requests, both sent and received, with notifications to alert you to new requests. |
Summary |
Activity is the engine of collaboration on Rundl. Activity provides a rich stream of temporally relevant information for participants to stay in the loop about what's going on across all their transactions. |
Communications |
Messages and comments are delivered into a global activity feed, or into a feed dedicated to each rundl. Updates to existing posts or new comments on messages stay in context and push the whole thread back to the most recent activity. |
Status updates |
All rundl status updates are delivered into global and rundl activity. Step status updates can be optionally sent to activity. Activity items leverage rich content such as video or images to create a social media style collaboration experience. |
Notifications |
Activity items are accompanied by email notifications which link back to the activity context. (Note notifications are configurable and can be controlled by user settings.) |
Pins |
Hosts can pin important messages to the "Pinned messages" sidebar in any rundl, for easy reference. |
Summary |
Organise work better with tasks, done the Rundl way. Go beyond just team collaboration and share work items with any participant in your transactions. |
Reminders |
Reminders provide a time-sequenced view of work assigned to any participant in your rundls. Assign a message in activity to a participant and set a reminder date. |
Summary |
Event based metrics provide insights about transactions hosted Rundl. Key metrics are presented in dedicated dashboards so members can better understand the performance of their processes. |
Rundls |
Get insights into growth in uptake of your services by tracking rundls started. |
Orders |
Get a real time view of orders to deliver services that you receive. See how many have been approved and declined. Also see how many related services are getting referred to your 3rd party referral partners from within your rundls. |
Summary |
Full text search provides really fast navigation across a range of entities on rundl. Search is global, so users can find information from any context navigating to search results switches context as required. |
Rich query language |
Power users can leverage our search engine's rich query language for powerful, targetted search. |
Filters |
Advanced search allows users to filter search results to just messages, comments, rundls, people, services and requests. |
Summary |
Rundl builds a number of applications that are available to all users so they can easily start using the Rundl platform. |
Web app |
Rundl delivers a full-featured, responsive web app for participants, hosts and administrators to use all the capabilities available in the underlying platform. The app runs in modern browsers and uses standard web technologies like HTML/CSS/JavaScript. The home screen is a good starting point for new users, showing just a list of recent transactions. For professionals using Rundl for work, the web app has advanced views to aid navigating and filtering across 1000s of transactions. A key feature is the work board, a Kanban-style board showing hosts an overview of an entire program of work in a single screen. |
iOS |
The Rundl iOS app runs on mobile and tablet devices from iOS version 8.0 and up. |
Text formatting |
Rundl apps support a simple syntax for formatting text as italic, bold, numbered and ordered lists, and external and internal links. |
Email bridge |
Participants can post messages or comments by emailing a special Rundl email address. To post messages, Rundl provides a unique email address for each specific transaction. To comment, each Rundl notification email for earlier comments or messages contains a reply-to address. Content is pulled from the email body and email attachments uploaded. |
Summary |
Add-ons extend Rundl's core collaboration with additional features and integrations that allow hosts to solve problems specific to their flow. |
DocuSign Electronic Signatures |
Rundl has partnered with DocuSign to deliver document signing. DocuSign enables people around the world to electronically sign documents, approvals, and agreements - on any device, in any time zone. |
Rundl Property AU |
Rundl Property AU adds Australian property details to your services. Collect property details with address validation and view the results on a map. |
Summary |
Rundl is an open platform for multi-party, multi-transaction process integration and collaboration. Rundl was architected from day one to support third party applications and integrations. Anyone can get access to the Rundl API to build applications that use or extend our core features. |
REST API |
The Rundl API is a RESTful Web API, providing programmatic access to resources representing relevant concepts on our platform. It includes URLs to access resources, leveraging built-in HTTP features to handle requests and return responses. |
Event subscriptions |
Rundl Event Subscriptions is a callback solution that enables your application to be called when an event of interest occurs on the platform. The solution involves subscribing to particular event types, which are sent to a target service in your own infrastructure that you manage. |
Embedded apps |
Embed your custom HTML5 web app in an iframe container on Rundl's web app at https://go.rundl.com for presentation layer integration. |