Expertise

    SharePoint for organisations in Zug.

    We support your SharePoint project from Bern and Sachseln. We agree with your team how to organise workshops, delivery and collaboration in Zug. Our first conversation focuses on your existing environment and the task you need to solve.

    01

    Chat in front, storage behind

    A project team discusses the next draft in a Teams channel; the file sits in the library of the related site, with versions, permissions and retention. The intranet, quality management and the contract register run on the same foundation, and content from the file server moves here. Later, Copilot and agents answer from the same content, with the permissions of the person asking.

    02

    Sites, teams, access, workflows

    We plan sites, navigation, metadata, teams and permissions as one whole and set them up with your content owners. Where one of our products covers the need, we use it, and extend only where your workflow calls for it. The building blocks:

    • Sites and navigationCommunication sites for information, team sites for work, hub sites that connect areas; metadata and views organise the libraries by task.Result: every document has a place, and search finds it there.
    • Teams lifecycleTemplates for projects and committees, rules on who creates a team and who may be a guest, archiving when a project ends.Result: every team has accountable owners and a planned end.
    • Permissions and guestsAccess through groups, sharing links with an expiry date, guests in separate areas and a regular review by the site owners.Result: for each site you can see who accesses what.
    • Approvals and workflowsReview, approve and reject with Power Automate or SP Approvals, also as the replacement for SharePoint Designer workflows.Result: every approval has an owner, a deadline and a history.
    • Content for CopilotClean up sharing, exclude sensitive sites through Restricted Content Discovery, set AI settings per site.Result: Copilot and agents answer from the content intended for them.
    • Existing environmentsInventory of sites, permissions and storage, a decision between Subscription Edition and Online.Result: for every site it is settled whether it stays, moves or is archived.
    03

    What your content owners bring

    Name one person per area who is responsible for the content, and show us typical documents, existing repositories and approval paths. We clarify guest access, retention and licences for your environment. If you plan Copilot, permissions are put in order first so that they match the content.

    04

    Tested with real tasks

    We test search, navigation and permissions with typical tasks and roles: does a new employee find the current policy, does a guest see only their project? For a migration, we compare inventories and document exceptions. Editorial upkeep and how changes are handled are agreed before go-live.

    05

    Arrange collaboration around the project

    Our offices are in Bern and Sachseln. Remote work and on-site meetings are arranged according to project needs. We clarify participants, working language, access and any travel effort beforehand. The location describes the service area, not an additional CNEXT office.

    Sound familiar? Tell us where you stand today.

    Contact in Zug

    Agree on a useful next step

    Tell us about your current workflow, the systems involved and the result you need. In our first conversation, we identify what else we need to know to plan a useful next step.