How MySkillsSpace works

Build a team around skills

Create a team, invite specialists, set the roles and publish shared services. Each of you keeps your own profile, and a client always sees who will actually do the work.

The flow

Create, invite, build the profile, publish, work together

Five steps, each a decision by a specific person, never by an automation. The details of each are further down the page.

  1. Create a team

    A specialist with a completed profile names the team, writes a headline and becomes its owner. The team starts as a draft nobody else sees.

    Read more
  2. Invite members

    The owner or a manager invites specialists by name, or by e-mail when they have no account yet. The invited person reads the role and any verification asked for, and accepts or declines themselves.

    Read more
  3. Build the team profile

    Roles say who may change what. The owner and managers fill in the description, the skills the team covers, its location and way of working; members keep their own profiles and privacy.

    Read more
  4. Publish a service or open a call

    A published team has a public page and offers team services in the same marketplace as personal ones, with the people who deliver always visible. It can also open its door to new members.

    Read more
  5. Start working together

    Clients write to the team in one thread that the owner and managers answer. Delivered work becomes case studies on the team page, and every member keeps their personal services beside the team's.

    Read more

Not every service is one person's work.

When several people deliver a project, the offer can show the team instead of pretending to be one specialist's service. A team on MySkillsSpace exists so that an offer tells the truth about who will do the work: one name, several specialists, each with their own profile.

Specialists apart. Skills together.

A team does not replace profiles. Each specialist remains a separate MySkillsSpace user with their own profile and services, and the team adds a shared professional context.

  • Your profile stays yours

    A team reads only your name, headline and photo from your profile. It does not edit it and publishes nothing in your name.

  • Several teams at once

    You can belong to any number of teams. The only limit is on teams you run as the owner: five active ones.

  • Personal services stay personal

    A team service is created separately, under the team's name. Leaving a team changes neither your services nor your profile. Only your name disappears from the list of contributors.

Create a team

Three fields to start. The rest of the team profile waits in its workspace.

Who can create a team
A Specialist account with a profile at least 90% complete. A team is a public page, and its first face is the person who founded it. A Company account neither creates teams nor joins them.
What is created
A team in draft, visible only to its members. The creator becomes the owner, and the team gets a public address derived from its name, which can be changed later in the settings.
What you fill in later
A logo, city and country, the work mode (remote, hybrid, on site), a website, the team's availability and whether it is open to new members. The name, headline and description can be changed at any time.
Publishing is a separate decision
The owner publishes the team once it has at least two members, a headline and a description. Only then does the team have a public page and can offer services. It can also be taken back to draft or archived.

Limits5 active teams you own25 members per team20 team services

Personal service and team service

The same editor, the same marketplace, a different provider. A client always sees who delivers the service.

Side by side in the marketplace

One search, two kinds of provider. The card says which is which.

  • One editor, two providers

    A team service is created by the owner or a manager in the same editor as a personal service: title, description, price, delivery, skills. There is one difference. The provider is the team, not a person.

  • Contributors from the roster

    A team service can name which members deliver it. The service page shows only those whose profile is public. Whoever leaves the team disappears from the list of contributors.

  • One marketplace, a clear source

    Both services land in the same catalogue and the same search results. A team service card says it plainly: Team, with the number of specialists. A team service lives under the team's address, never under a member's profile.

  • Publishing is news for everyone

    When a team service is published, every member gets a notification. The team offers as a whole, so everyone whose name may appear on the service knows it is now public.

In detail

How each part works

The rules behind the five steps: invitations and verification, roles and permissions, the public page, privacy, contact and the team's history. Open the one you need.

Invite. The other side decides.

An invitation is explicit and specific: who is inviting, to which team and in which role. Membership is never created automatically.
  1. Owner or manager

    Picks a person and a role

    Searches for a specialist by name or headline and proposes a role: member or manager. Someone without an account is invited by e-mail. That invitation waits for them after they register.

  2. Invited specialist

    Reads and decides

    In My Teams they see the team's name, who is inviting, the proposed role and any verification requirements. They accept or decline. An invitation waits 30 days, and until then the inviter can withdraw it.

  3. The team

    Membership exists after acceptance

    After accepting, the specialist is on the member list in the proposed role, and the inviter gets a notification. After declining, nothing changes, and the team can invite that person again later.

A notification on MySkillsSpace and an e-mail reach the invited person right away. One person has at most one live invitation per team.

An invitation can carry verification requirements

The same mechanism that works in recruitment. The team asks for evidence of skills, and the invited person sees it before answering.

  • Attached by the owner or a manager

    Up to five assessments, each marked required or optional. Before sending, the inviter confirms that they reviewed the assessments' structure and chose them deliberately. An e-mail invitation goes without requirements.

  • Accepting starts nothing

    After accepting, the specialist is already on the team, and the assessments wait in their panel. An assessment starts only when they press start themselves.

  • Reuse comes first

    Where the requirement allows it, a valid public verification is recognised the moment the invitation is sent, and a private one can be applied by the invited person with one click. Nobody sits the same assessment twice for no reason.

  • Results go to the authorised

    The result reaches the people who manage invitations: the owner and the managers. It settles nothing by itself. The assessment is evidence, and the decisions in a team are made by people.

Roles and permissions

Three roles: owner, manager and member. Membership does not automatically give the right to manage the team.

Owner The owner runs the team: publishes it, changes roles, transfers ownership and archives it. There is exactly one per team, and they cannot leave without handing ownership over.

Action Owner Manager Member
Profile and publication
Edit the team profileYesYesNo
Publish the team and take it back to draftYesNoNo
Team availabilityYesYesNo
Archive and restoreYesNoNo
Roster
Invite specialistsYesYesNo
Pending invitations and verification requirementsYesYesNo
Open to members and join requestsYesYesNo
Remove members of lower rankYesYesNo
Change rolesYesNoNo
Transfer ownershipYesNoNo
Leave the teamNoYesYes
Offer and contact
Team services: create, edit, publishYesYesNo
Order of services in the catalogueYesYesNo
Portfolio and case studiesYesYesNo
Answer clients in the team's nameYesYesNo
  • Rank works one way. A manager removes only members, never another manager or the owner. The owner can act on anyone but themselves.

  • Ownership is handed over, not taken. The owner offers it to one member, who accepts or declines. The previous owner becomes a manager.

The team page, as a client sees it

Once published, the team has its own public address. Everything on that page the team wrote itself or published as a service.
  • Identity and description

    Name, headline, logo, description, city and country, work mode, website. Plus availability: now, from a given day, limited or none, with one sentence from the team.

  • Capabilities from services, not from profiles

    The list "What this team does" is the skills attached to the team's published services. It is not a sum of member profiles and carries no percentages. It is what the team offers, not a score for how well it does it.

  • Services and case studies

    The team's published services and case studies: project name, the outcome in one sentence, description, period, skills and contributors from among the members. Drafts are seen only by members.

  • Members and the open door

    The member list shows only people with a public profile, but the number of specialists is always real. A team open to new members lists the skills it lacks, and a specialist can ask to join.

  • How a client finds the team

    The team directory is searched by name, headline or skill and filtered by capabilities, availability, work mode, location and openness to members. The team also appears in search suggestions and beside its services in the marketplace.

A team does not take control of your profile

Joining a team does not widen your profile's audience. Visibility settings work inside a team the same way they work everywhere else.
  • Your name as you set it

    If your profile shows only "Anna K.", the team also sees "Anna K.". The same rule applies to invitations, services and case studies.

  • The team sees the minimum

    Your name, headline, photo and role. It does not see contact details, salary expectations or documents from your profile.

  • Public only with a public profile

    On the team page, on a service and in a case study you appear only when your profile is public. Otherwise the page shows the real number of members, but not you.

  • Leaving without a trace

    When you leave or are removed, your name disappears from the contributors on services and case studies. The team's work stays, with one name fewer.

A conversation with the team, not another messenger

The team is one side of a conversation with a client. MySkillsSpace adds no internal chat, task boards or video calls to that.
  • The thread belongs to the team

    A client writes to the team about a specific service, or without one, from the team's page. The conversation is between the client and the team, not with whoever happened to open it. A change of owner does not take the thread away.

  • The authorised answer

    The owner and the managers answer in the team's name and only they see its inbox. The client sees the team's name, not the person who typed. An ordinary member has no access to the team's conversations.

  • The team knows who answered

    On the team's side, every reply shows which member wrote it. The client does not see that. The team keeps a trail of accountability, and the client has one correspondent.

  • What is not here

    No internal team chat, task boards, time tracking or meetings. For the project work itself the team uses its own tools. MySkillsSpace handles the presentation and the first contact.

A team is not a Company account

Two different things on the same platform. One offers work, the other looks for it.

Specialist team

  • A group of Specialist accounts that offers work together
  • Formed through invitations. Has an owner, managers and members
  • Publishes team services and case studies, answers clients as the team
  • Does not recruit, does not hire and is neither an employer nor a separate entity

Company account

  • A separate account type for an organisation, with its own company profile
  • Discovers specialists and teams, browses their services
  • Sends recruitment invitations and runs processes with stages and assessments
  • Neither creates specialist teams nor joins them. Can write to a team and ask about its service

MySkillsSpace creates no contract or joint entity between the members of a team and signs no agreement with a client in anyone's name. A team is a way of presenting who offers work together and who does it. The terms of working together are set by the people involved.

From an idea to the first enquiry

One team, step by step, on the product's screens.
  1. Anna

    Creates Northstar Studio

    Anna's profile is 92% complete, so the Create team button is live. She enters a name, a headline and a description. The team is created as a draft, and Anna is its owner.

  2. Anna

    Invites Marek and Julia

    Marek has an account, so Anna finds him by name and proposes the member role. Julia has no account yet. She gets the invitation by e-mail and will find it in My Teams once she registers.

  3. Marek and Julia

    Accept

    Each of them sees the invitation in My Teams and accepts it separately. Anna gets two notifications. The team now has three members.

  4. Anna

    Sets the roles

    Julia will run the offer, so Anna changes her role to manager. Marek stays a member: he is on the team, but does not run it.

  5. Anna

    Publishes the team

    The team has a headline, a description and three members, so the list of blockers is empty. Anna publishes. From this moment Northstar Studio has a public page and appears in the team directory.

  6. Julia

    Publishes a team service

    As a manager, Julia creates the service Web application development, names the contributors and publishes it. Every member gets a notification, and the service reaches the marketplace under the team's name.

  7. TechCorp

    Finds the service and writes

    The company comes across the service in the search results and writes to the team. The thread belongs to Northstar Studio. Julia or Anna answers, and TechCorp sees the team's reply.

  • The team workspace: an overview with counters, profile, members, services, portfolio and settings.
  • Invitations with a role and optional verification requirements, a list of pending ones that can be withdrawn, join requests to accept or decline.
  • Team services and case studies: draft, publish, pause, order in the catalogue.
  • The team inbox: conversations with clients held in the team's name, showing which member answered.
  • Owner only: changing roles, offering to transfer ownership, publishing the team, archiving and restoring.

Frequently asked questions

Who can create a team?

A Specialist account with a profile at least 90% complete. The creator becomes the owner. One person can own at most five active teams. A Company account does not create teams.

Does joining a team replace my specialist profile?

No. Your profile, skills and personal services stay yours. The team reads only your name, headline and photo from your profile and adds a separate context: the team page and team services.

Can I belong to more than one team?

Yes, without a limit. Only the number of teams you run as the owner is limited: five active ones.

Who can invite new members?

The owner and the managers. A member does not invite. You can invite a specialist with an account or any e-mail address. An e-mail invitation waits for registration.

Do I have to accept an invitation?

Yes. Membership exists only after acceptance. You can decline without giving a reason, and an unanswered invitation expires after 30 days.

Can every member edit the team?

No. The profile, services, portfolio, availability and invitations are changed by the owner and the managers. A member sees the team workspace but does not change it.

How do roles and permissions work?

There are three roles. The owner can do everything, including changing roles, transferring ownership, publishing and archiving the team. A manager acts on the team's behalf: profile, invitations, services, portfolio, inbox. A member is on the team and can leave it. There is exactly one owner, and they cannot leave without handing ownership over.

Can a team publish its own services?

Yes, once the team is published. Team services are created by the owner and the managers, up to 20 per team, in the same editor as personal services. The provider is the team.

How does a team service differ from a personal one?

By the provider. A personal service sits on the specialist's profile and says who delivers it. A team service sits under the team's address, is marked Team with the number of specialists, and can name contributors from among the members. Both land in the same marketplace.

Can a skills verification be attached to an invitation?

Yes. The owner or a manager attaches up to five assessments, each required or optional, and confirms their scope before sending. The invited person sees the requirements before deciding. This applies to invitations to existing accounts. An e-mail invitation goes without requirements.

Does accepting an invitation with assessments start an assessment?

No. After accepting you are on the team, and the assessments wait in your panel. An assessment starts only when you press start. A valid verification you already hold can be applied instead of a new attempt, if the requirement allows it.

Who sees the results of such a verification?

The people authorised to manage invitations, that is the owner and the managers, next to the invitation in the team workspace. The result is evidence, not a decision. Nobody is removed or promoted automatically.

Does the team see my private data?

No. The team sees your name in the form you set in your profile, your headline, photo and role. It does not see contact details, salary expectations or documents. On the public team page you appear only with a public profile.

Is a team the same as a Company account?

No. A Company account is a separate account type for an organisation that looks for specialists and recruits. A team is a group of Specialist accounts that offers work together. A Company account does not create teams, but it can write to them and ask about their services.

Does MySkillsSpace have an internal team chat?

No. A team holds conversations with clients: the thread belongs to the team, and the owner and the managers answer. There is no chat between members, no task boards and no video calls.

How does a client contact a team?

From the team's page or from the page of one of its services, with the Send message button. You need to be signed in, and a Company account is enough. The conversation lands in the team inbox, and the client gets a reply from the team.

Can I leave a team?

A manager and a member can leave at any time, from the team workspace. The owner first offers ownership to another member. Nothing changes until that member accepts, and then the previous owner becomes a manager.