Skip to content

Salesforce Customisation · Oxford

Salesforce Customisation in Oxford

Configuring Salesforce for how Oxford teams actually work, most of which is the access model. Visibility is computed from several layers at once — object permissions, field permissions, org-wide defaults, role hierarchy, sharing rules — and it is entirely possible to grant something at one layer that another silently withholds.

Why this comes up

The problem

Users cannot see records they need, someone widens a permission to fix it, and now everyone can see everything.

What you get

What we deliver

  • Access designed as a model rather than adjusted per complaint
  • Permission sets used for capability, with profiles kept minimal
  • Org-wide defaults set restrictively and opened deliberately by sharing rules
  • Record types and layouts reflecting genuinely different processes, not preferences
  • Field-level security applied where data should not be visible to everyone
  • Configuration favoured over code wherever the platform supports the requirement

Want this scoped for your business in Oxford?

Thirty minutes, no charge, no sales script. You leave with a written summary of what salesforce customisation would actually involve — whether or not you use us.

Book a 30-minute call

Working in Oxford

South East

Oxford's economy runs on research and life sciences, and a lot of the work here starts with a research group or spin-out that needs a prototype turned into something other people can safely use.

Research groups and spin-outs needing a prototype turned into a supportable product make up most of the local demand.

Sectors we work with in Oxford

  • Research & Higher Education
  • Life Sciences
  • Publishing
  • Technology
  • Tourism

What we work with

Technologies and platforms

  • Salesforce
  • Flow
  • Lightning App Builder
  • Apex

Who we work with

Industries we serve

  • Financial services
  • Manufacturing
  • Professional services
  • Nonprofits
  • Technology companies

Why us

Why Oxford businesses choose Asionis

  • Projects typically launched within 4–8 weeks
  • No long-term contracts required
  • All team members UK-based
  • Dedicated account manager and development team
  • Transparent reporting with monthly performance metrics
  • Scalable from startup to enterprise

How we work

  1. Step 1

    Free consultation

    A 30-minute call to understand the problem. You keep the written summary either way.

  2. Step 2

    Proposal

    Scope, timeline and a fixed price, in writing, before anything starts.

  3. Step 3

    Build

    Short cycles with regular check-ins, so you see progress rather than hear about it.

  4. Step 4

    Launch and support

    We handle the go-live and stay available afterwards.

Salesforce Customisation in Oxford — common questions

Why is the sharing model so easily broken?
Because fixes are applied at whichever layer is quickest. Someone widens an org-wide default to solve one user's problem, and the effect reaches every record of that type. Access needs to be designed once and changed against that design, not patched.
Profiles or permission sets?
Permission sets for what someone can do, profiles kept as a thin baseline. Cloning profiles for every variation produces dozens that nobody can compare, whereas permission sets are additive, inspectable and can be granted temporarily.
When do we need record types?
When the process genuinely differs — different stages, different required fields, different picklist values. Creating record types because two teams want different layouts is a maintenance cost that compounds with every future change.
How much should we customise?
Less than most organisations do. Every customisation is something to test through three releases a year and to explain to the next administrator, and a good proportion of what gets built exists because nobody challenged a requirement. The useful discipline is asking what breaks if a request is refused — often the honest answer is that a team would have to change a habit, which is a cheaper outcome than a permanent addition to the org.
Do you work with businesses across Oxfordshire?
Yes. We are based in Leicester, United Kingdom and work with clients throughout South East, including Oxford and the surrounding Oxfordshire area. Most collaboration happens remotely, and we travel for kick-offs and key milestones.
What kind of Oxford businesses do you usually work with?
Research groups and spin-outs needing a prototype turned into a supportable product make up most of the local demand. Beyond that we work across Research & Higher Education, Life Sciences, Publishing, Technology and Tourism.
Do you cover the areas around Oxford?
Yes — we work throughout South East, including Reading, Milton Keynes, Cambridge, London. Oxford is an urban area of roughly 170,000+, and we take on work across the wider Oxfordshire region rather than the city boundary alone.

Talk to us about Salesforce Customisation in Oxford

A 30-minute call with someone who would actually work on it. No sales script, no obligation.

  • Projects typically launched within 4–8 weeks
  • No long-term contracts required
  • All team members UK-based
  • Dedicated account manager and development team
  • Transparent reporting with monthly performance metrics
  • Scalable from startup to enterprise

Or reach us directly

07707 771599admin@asionis.com

Leicester, United Kingdom